A batched job that selects rows in error or pending under an attempt cap, plus stale claims older than ten minutes, ordered oldest-attempt first, and re-runs each at its last desired status.
Also called: QuickBooks sync failed · retry sync · eventual consistency
- 1The cron queries rows needing a retry in one OR query.
- 2Stale 'syncing' claims older than ten minutes are reclaimed.
- 3Each row is re-run at its current app status.
- 4Rows that exceed the attempt cap stay in error for the retry chip or a manual fix.
The route names each failure mode it covers: 'The two triggers (contract countersign, Start Project) fire-and-forget, so a transient QBO outage, an expired token, a not-yet-connected org, or a serverless instance killed mid-flight can leave a quickbooks_project_links row un-synced with no user-visible failure.' The cap exists so 'permanently-broken rows (e.g. no contact) [do not] spin forever'.
- Fire-and-forget triggers left silent gaps when anything went wrong.
- A crashed run left rows claimed forever.
- Permanently broken rows would retry indefinitely.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →