Two halves. A small status chip reads the job's sync link row and turns an otherwise-silent background operation into a visible signal with a manual retry. A scheduled sweep independently re-drives rows that errored, were never synced, or were left mid-claim by a crashed process.
Also called: quickbooks sync failed · retry quickbooks · did it sync · sync error
- 1The chip renders nothing when there is no link row or QuickBooks is not connected, so it is safe on any job card.
- 2The sweep picks up error and pending rows under an attempt cap, plus 'syncing' claims older than ten minutes, oldest attempt first.
- 3Each row is re-run at its last desired status.
- 4A capped attempt count stops a permanently-broken row spinning forever; it stays in error for the chip and a manual fix.
The sync fires in the background, so a brief outage, an expired token or a server dropped mid-request left a job unsynced with nothing on screen to say so — found weeks later, when the bookkeeper cannot locate the project. A sweep retries anything left behind, and every job shows its sync state on the record, which turns an invisible background process into something a builder can see and act on.
- Silent failures in a background integration.
- No way to retry a failed sync without support.
- Rows stuck mid-sync after a process was killed.
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 →