Why did my integration stop syncing?
Short answer
An integration that stops syncing is almost always an expired authorization, a changed field mapping, or a rate limit on the connected tool's side. Check the integration's connection status and error log first, since it usually names the exact reason before you touch any settings.
Before you start
- The name of the integration and roughly when syncing stopped.
- Access to the integration's connection and error log.
- Login access to the connected third-party tool.
- Knowledge of any recent changes to fields or mappings.
Step by step
- 1
Check the integration's connection status
Look for a disconnected, expired, or error state on the integration itself.
Most sync failures show a clear status flag before you need to dig any deeper.
- 2
Reauthorize the connection if needed
Many integrations require periodic reauthorization that can silently expire.
An expired authorization is one of the most common and easiest fixes for a stalled sync.
- 3
Review the error log for the specific failure
Look for a message tied to the exact record or field that failed to sync.
A specific error points directly at the fix instead of leaving you guessing.
- 4
Check for recent field mapping changes
Confirm that a renamed or removed field on either side did not break the mapping.
A mapping that once matched can silently break the moment either side changes.
- 5
Check the connected tool for its own outage or limit
Log into the third-party tool directly to confirm it is not experiencing its own issue.
The problem is not always on your side, and checking both ends saves wasted troubleshooting.
- 6
Look for a rate limit or throttling message
High volume syncs can hit a limit on the connected tool that pauses further updates.
A rate limit resolves on its own after a cooldown but explains a temporary full stop.
- 7
Run a manual sync or test record
Trigger a single test sync after making a fix to confirm the connection is fully restored.
A successful test confirms the fix instead of hoping the next automatic sync works.
What good looks like
- The exact cause of the sync failure gets identified instead of guessed at.
- Authorization and field mapping issues get caught before they cause bigger gaps.
- Both sides of the integration get checked, not just the platform.
- A confirmed test sync proves the connection is genuinely restored.
Common mistakes
The ways this goes wrong in support, and what to do instead.
Disconnecting and reconnecting without checking the error›
The same root cause, like a broken field mapping, breaks the sync again right away.
Do this instead: Read the specific error message before reconnecting anything from scratch.
Only checking one side of the integration›
Time gets spent on the platform side while the actual outage is on the connected tool.
Do this instead: Log into the third-party tool directly to rule out an issue on its end.
Assuming a rate limit means something is broken›
A temporary throttle gets treated as a permanent failure and triggers unnecessary rebuilding.
Do this instead: Check for rate limit messages and allow a cooldown period before troubleshooting further.
Frequently asked
6 questions about fix an integration that stopped syncingRelated guides
Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.
Do this next
The natural follow-on tasks once this one is working.
People usually get here from
Guides that lead into this one, in case you skipped a step.
More in Support
Nearby tasks that share the same setup and vocabulary.
Was this guide helpful?
Tell us what worked and what didn't. It shapes what we rewrite next.
You didn't get into business to be in the tech business.
Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.