CRM update failed: CRM connection needs reconnecting
Last updated: October 2, 2026
Applies to: Super Admins, Creators, and Integrators, with Salesforce or HubSpot connected
Project automations are available when they're turned on for your organization. If you don't see an Automations tab on your projects, contact your OnRamp team.
This CRM update failed because OnRamp couldn't use its connection to your CRM. In the project's Logs, the Update Salesforce Field or Update Hubspot Field row has an X in Success. Payload shows the fields OnRamp tried to send. Error says the CRM session expired or isn't valid, or that the CRM refused OnRamp's sign-in. On connections that OnRamp keeps signed in itself, the message can start with token fetch failed.
Why it happens
OnRamp signs in to Salesforce or HubSpot through the integration on Settings > Integrations+. If that sign-in stops working, for example because access was revoked in your CRM, CRM updates fail until the integration is reconnected. The integration can still show Enabled on Integrations+ while this happens.
Some failures are temporary instead: your CRM's request limit was reached, or the request timed out or lost its connection. These clear up on their own, but the automation doesn't run again by itself.
Fix it
If the failure was temporary, wait, and then repeat the event on the project. To reconnect the integration:
Go to Settings > Integrations+.
Select your Salesforce or HubSpot integration. Its Details tab opens.
In the Configure row, select Reconfigure Integration. If there's no Configure row, OnRamp keeps this connection signed in itself, so contact support to reconnect it.
For Salesforce, in Instance auth setting, select the option that matches your Salesforce org.
Select Confirm.
In the window that opens, sign in to your CRM and approve access for OnRamp.
Back in OnRamp, wait while the dialog finishes. OnRamp confirms when the integration is configured.
Repeat the event on the project. Then, in Logs, select Refresh to see the new row.
Warning: Don't disconnect the integration to fix this. Disconnecting removes the links between your projects and their CRM records. CRM updates then fail until each record is linked and selected again, as CRM update failed: no CRM record selected describes.
Still stuck?
Contact support with the project's name and link, the row's Timestamp, the text from Error, and which CRM the integration connects to. Say whether its Details tab has a Configure row.