Troubleshooting
Getting a Bad Refresh Token error
If the OutboundSync app is not connected to your CRM, the app will not have authorization to sync data to your HubSpot portal or Salesforce instance.
When to use this guide: Use this guide when expected sync behavior is missing, delayed, or incorrect.
If the OutboundSync app is not connected to your CRM, the app will not have authorization to sync data to your HubSpot portal or Salesforce instance.
In the error console, this will appear as an HTTP-Code: 400 error with a BAD_REFRESH_TOKEN.
For HubSpot users, check to ensure that the OutboundSync application is installed in the HubSpot Marketplace , as the app must be connected to your portal to authorize data syncing.
For Salesforce users, open Connected accounts → Salesforce, check whether the profile shows Connected or Not connected, then click Connect or Reconnect on that row. Full steps: Re-authorize your Salesforce account. For initial Connected App setup, see the Salesforce setup guide.
What happens to syncing until you reconnect
Section titled “What happens to syncing until you reconnect”A missing or invalid refresh token means every sync to that CRM would fail. So OutboundSync pauses CRM sync for each source on the connection after the first auth error, and it sends a sync.failed webhook if you subscribe to one. Events that arrive while sync is paused are still logged, with an Error status and the Error Response sync_circuit_open.
Reconnecting the CRM resumes syncing for new events. Events from the outage aren’t replayed automatically. See How to reprocess errored webhook logs to push them to your CRM.
