Get started with a free trial today
Already have an account? Sign in
Replication Frequency is a type of replication scheduling that runs replication jobs based on a time interval you specify.
In this guide, we’ll cover:
Replication Frequency is available for all database and SaaS integrations.
The Replication Frequency setting, found in the Integration Settings page, defines how often Stitch will attempt to extract data from an integration. For example: If set to30 minutes, Stitch will attempt to connect to and extract data from the integration every 30 minutes.
After you define and save the integration, Stitch will update the integration’sSync Status toPending. This status indicates that Stitch is in the process of scheduling a replication job for the integration.
Note: For newly created integrations, scheduling a replication job can take up to 30 minutes. You can alsomanually start a job, but note that this will determine howongoing replication jobs are scheduled.
Ongoing replication jobs are scheduled based on the start time of the previous job.
If a job runs over into the next recurrence of the selected Replication Frequency, it will be skipped. Jobs will resume at the next Replication Frequency interval. Refer to the next sectionfor an example.
In this example, we’ll look at the potential schedule for an integration with a Replication Frequency of6 hours.
Based on these settings, Stitch will kick off a replication jobevery 6 hours. The schedule for this integration might look like this:
| Job # | Start Time (EST) | Start Time (UTC) |
| 1 | 09:00:00 | 13:00:00 |
| 2 | 15:00:00 | 19:00:00 |
| 3 | 21:00:00 | 01:00:00 |
| 4 | 03:00:00 | 07:00:00 |
| 5 | 09:00:00 | 13:00:00 |
In this example, we’ll look at how a job can be skipped due to a previously long-running job. This can occur when a job takes longer to run than the selected Replication Frequency.
Based on these settings, Stitch will kick off a replication jobevery hour. The schedule for this integration might look like this:
| Job # | Start Time (EST) | Start Time (UTC) | End Time (EST) | Duration |
| 1 | 02:30:00 | 18:30:00 | 03:25:00 | 55 minutes |
| 2 | 03:30:00 | 19:30:00 | 04:38:00 | 68 minutes |
| 3 | Job | is | skipped | - |
| 4 | 5:30:00 | 21:30:00 | 06:21:00 | 51 minutes |
| 5 | 06:30:00 | 22:30:00 | 07:01:00 | 31 minutes |
In this example, Job 3 (scheduled for04:30:00) was skipped because Job 2 took longer than the Replication Frequency (1 hour/60 minutes) to complete. Replication then resumed on the next recurrence of the Replication Frequency, which was at05:30:00.
Note: Stitch doesn’t currently send or display notifications when a job is skipped.
You can create an interval schedule using Replication Frequency in an integration’sSettings page.
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.