Nightly Resync
Backfill delayed source data with an automatic daily 24-hour resync.
Nightly Resync is an optional safety net for pipelines whose source devices may upload data late. When enabled, IMSURGE runs an additional execution each day and requests the previous 24 hours of source data.
Why Use Nightly Resync?
Devices with weak cellular connections or unreliable power may not upload readings in chronological order. When a device reconnects, it may make its newest readings available before older readings.
For example:
- A device goes offline at 4:00 PM and reconnects at 5:00 PM.
- The source makes the 4:50–5:00 PM readings available first.
- A pipeline execution at 5:00 PM retrieves those readings and continues forward from 5:00 PM.
- The device uploads the 4:00–4:50 PM readings later, after that execution has finished.
Without another request for the earlier period, the delayed readings could leave a gap. Nightly Resync requests the previous 24 hours again, giving those readings another opportunity to pass through the pipeline.
Nightly Resync reduces the likelihood of gaps but does not guarantee a complete dataset. Data delayed by more than 24 hours, unavailable from the source API, or affected by a failed execution may need to be recovered with a manual execution using a supported Backtrack window.
How It Works
When Nightly Resync is enabled, IMSURGE:
- Starts one additional pipeline execution at 12:00 AM UTC each day.
- Requests source data from the previous 24 hours.
- Processes the retrieved data through the pipeline’s existing source and target configuration.
- Leaves the pipeline’s regular polling schedule unchanged.
The resync appears as a separate execution in the pipeline’s execution history. If a regular execution is also due at midnight UTC, you may see both executions begin close together.
Because the 24-hour window overlaps earlier executions, some retrieved readings may already exist in the target platform. How existing or duplicate readings are handled depends on the source and target integrations.
Availability
Nightly Resync is available when all of the following are true:
- The organization has an IMSURGE Pro account.
- The source integration supports scheduled polling and at least 24 hours of backtracking.
- The pipeline has a polling frequency other than Manual Only.
- The pipeline has not reached its expiration date.
The setting is shown only for supported source integrations. If the setting does not appear, the selected source or account does not support Nightly Resync.
Enable Nightly Resync
You can enable the feature while creating a pipeline or from an existing pipeline’s settings.
New Pipeline
- Go to Pipelines and select + Pipeline.
- Select a supported source integration and a target integration.
- Under Execution Settings, choose a polling frequency other than Manual Only.
- Set Nightly Resync to Enabled.
- Finish configuring and save the pipeline.
Existing Pipeline
- Open the pipeline and select Edit Settings.
- Confirm that the pipeline has an active polling frequency.
- Set Nightly Resync to Enabled.
- Save the changes.
To stop the additional daily execution, return to the pipeline settings and set Nightly Resync to Disabled.