Deferred Data Ingestion
If the Source system does not contain any new Events to be ingested, Hevo defers the data ingestion for a pre-determined time. Hevo re-attempts to fetch the data only after the deferment period elapses.
Hevo uses the ingestion results as feedback to decide the deferment period:
If no Events are fetched from the Source during the first attempt, Hevo defers the data ingestion for a short duration of time. For example, five minutes. This time is referred to as the deferment period.
Note: Hevo automatically assigns a value for the deferment period.
Once the initial deferment period has elapsed, Hevo re-attempts to fetch the Events from the Source.
If no Events are fetched in the subsequent attempt, Hevo increases the deferment period. For example, 10 minutes.
Each time data ingestion gets deferred, the deferment period increases.
Note: The maximum deferment period allowed for data ingestion is six hours. Therefore, the deferment period is not applicable if the data ingestion frequency is more than six hours.
If Hevo fetches any Event(s) in any subsequent attempt, the deferment period is reset to zero.
The following Sources support deferment of data ingestion:
- Google Drive
- Google Ads
- Google Cloud
- Google Play Console
- Databases (Except log-based fetching tasks)
Overriding the Deferring of Data Ingestion
You can request Hevo to never defer ingesting data from a Source. Contact Hevo Support for more details.