Salesforce connection shows an error or says token expired
Your Salesforce integration displays a connection error or an expired token warning in Settings. CRM syncs fail and deal data stops updating. Reconnecting with the right Salesforce user permissions usually resolves it.
The Salesforce connection card shows a red error badge or a message that the access token is expired or the session is invalid. Sync jobs for CRM data are failing and attribution numbers have stopped updating.
Why this happens
Salesforce OAuth sessions expire when a Salesforce admin resets the connecting user's password, when a session policy forces periodic token rotation, or when the connected user's profile loses API access. Tokens can also become invalid if the Salesforce sandbox was refreshed and the credentials now point at a stale org.
How to fix it
- Go to Settings and Connections. If a broken Salesforce entry is showing, click Disconnect to clear it before reconnecting.
- Confirm the Salesforce user you plan to reconnect with has the API Enabled permission in their Salesforce profile. Without it, every sync will fail immediately.
- Confirm that user has read access to Accounts, Contacts, Leads, Opportunities, and the standard fields Revenue Proven reads.
- Click Connect Salesforce and complete the OAuth flow as that user.
- After reconnecting, check the Connections page and confirm the status switches to Active.
- Trigger a manual sync and watch the progress indicator. The first CRM pull after reconnecting may take a few minutes.
- If your Salesforce org enforces an IP allowlist, verify Revenue Proven's server IPs are in the trusted range. Contact support for the current IP list.
Still stuck?
Share your Salesforce org URL and the full error message text with our support team. We can identify whether the issue is a permission gap, an IP restriction, or an API rate limit.