Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Scheduling improvement

Reuben Gerald User

Hello Team,

We have a connector that takes an average of 5 mins to sync and we have one of our downstream teams that consume the data at 30 mins.

Currently we have set the connector sync frequency as 15 mins.

The issue we face is that sometimes a particular sync takes more then 15 mins and fivetran seems to perform the next sync after the current sync time + 30 mins. It skips the run ofr the next 15 min schedule since the current run has run over.

Could you update the scheduling to include 10 mins in the window or work on a feature wherein fivetran performs the next run immediately after the current run is complete (when the current run exceeds the schedule frequency).

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Lyndsey User

    Hi Reuben, 

    Thanks for the feedback!

    We describe how this works in our documentation, but to summarize, if a sync isn't finished at the time the next sync is meant to start, we skip that sync and go the next scheduled time. So in your case, if we assume the sync starts at 8am and finishes at 8:20am, the next sync at 8:15am would be skipped, but we would resume the normal schedule at 8:30am. From your description, it sounds like your data team would be expecting for the sync second sync to have been done before 8:30. 

    There's a couple ways we could try to solve for this – first, can you help me understand what you mean about including 10 mins in the window? Do you mean a sync frequency of 10 mins? 

    Also, do you use our REST API? The API allows you to create custom sync schedule. Learn how in our How to Set a Custom Sync Frequency Troubleshooting page.

    Best, 

    Lyndsey