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

Community

Other: Pause or Cancel Historical Re-Sync

Ardis Miller User

We currently have a Re-sync that has been running for eight days. The sync is requesting an increase in API limit. In order to control raising cost we would like to avoid increasing the API limit. d rather pause OR cancel the sync we see which object the sync hung on so if we could stop this re-sync...start a new resync just for this object our data would be caught up.

 

 

 

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Michael Lisin User

    We would like to get "Cancel Historic Resync" feature as well.

  • Lyndsey User

    Hi Ardis, I am hoping that the historical sync has concluded now! 

    Out of curiosity, did you figure out if there was a specific object in this case that was causing the delay? 

  • Lyndsey User

    Michael, I'd also love to know why you'd want the 'Cancel Historic Resync' feature? Is this use case similar to the one described above where it was taking too long? 

  • Michael Lisin User

    @Lindsey. 

    Yes, this is one of the scenarios.

    The other scenarios in the same category:

    • Someone made a mistake pushing a historical sync, some of our syncs can last > 20 hours 
    • Fivetran recommended historic resync and then an alternative better solution
  • Ray Qureshi User

    Chiming in. I work at a very large corporation. We encountered the exact same failure mode described by Michael Lisin, where the historical backfill was accidentally triggered and it took 20+ hours and we were told that the only thing we could do was to wait. The lack of this feature resulted in a major incident. Our internal teams had to be paged and operationally handle the impact of delayed data including customer outreach.