Missing Enthuse Data
If you notice that expected Enthuse data has not appeared in MoveData or Salesforce, this article explains the known causes and how to resolve them.
The issue#
Enthuse data may be missing or delayed in Salesforce. This most commonly affects recurring donations taken via direct debit, but can occur with any data type.
Note
This is a known platform limitation on the Enthuse side, not a MoveData configuration issue. Enthuse has acknowledged these limitations and has plans to address them with new APIs.
Why this happens#
MoveData uses a polling integration with Enthuse, requesting data at configurable intervals (between 10 minutes and 24 hours). When MoveData polls Enthuse, it requests all transactions since the last successful download.
Enthuse has an infrequent issue with releasing data in a timely manner. When there is a delay on the Enthuse side, data can miss the polling window -- MoveData requests data for a time range, but the delayed records have not yet been made available by Enthuse's API.
Root cause#
Enthuse's current API does not support querying transactions by last modified date. This means that if data is delayed internally within Enthuse, MoveData has no way to detect or retrieve it after the polling window has passed.
Enthuse could resolve this by allowing queries by last modified date and setting that value at the time the data becomes available via the API. This is a planned feature of their new APIs.
MoveData's mitigation#
Since April 2025, MoveData applies a 24-hour overlap to all Enthuse polling requests. This means each poll requests all data since the last successful download plus 24 hours.
For example, if MoveData last downloaded data at midnight on 5 January, the next poll requests all transactions from midnight on 4 January. This overlap captures most delayed records automatically.
Success
The 24-hour overlap is applied automatically. You do not need to configure anything to benefit from this mitigation.
How to fix it#
If you suspect data is missing:
- Identify the date range where data appears to be missing.
- Cross-check against Enthuse to confirm the records exist in the platform.
- Contact MoveData at support@movedata.io and provide:
- Your integration ID — you can find this by opening your Enthuse integration in the MoveData app and copying the ID from the browser URL
- The suspected date range
- Any specific transaction or donation references you can identify
MoveData will queue a catchup job that imports all available data from the specified date range via the Enthuse API.
Affected data types#
While any data type can be affected, the most commonly impacted are:
| Data type | Frequency of issue |
|---|---|
| Recurring donations (direct debit) | Most common |
| One-off donations | Infrequent |
| Campaign data | Rare |
| Contact data | Rare |
Future improvements#
Enthuse has indicated that their new APIs will address these data delivery issues by supporting last-modified-date queries. MoveData will update the Enthuse integration to use the new APIs when they become available.