Qobra Incident History

This incident is now resolved. Summary: an error in how our system handled Salesforce's security token rotation during data syncs could cause some Salesforce integrations to become disconnected, requiring a re-authentication. What we did: we fixed the token renewal process so it can no longer invalidate a Salesforce connection, hardened the sync pipeline so token renewals happen safely before each sync rather than during it, and deployed proactive monitoring on Salesforce connection drops so our team is alerted immediately if an integration loses its connection. Token renewals and data syncs have been running normally across all workspaces since the fix was deployed. If your Salesforce connection is still disconnected, an admin can restore it in Settings → Integrations → Salesforce by re-authenticating — and our support team is available if you need any help.

A fix for the Salesforce connection issue has been deployed. The root cause was an error in how our system handled Salesforce's security token rotation during data syncs, which could cause some Salesforce integrations to become disconnected. New token renewals are now handled safely and data syncs are running normally. However, workspaces whose Salesforce connection was invalidated before the fix will need to reconnect: an admin can do so in Settings → Integrations → Salesforce by re-authenticating. If you're unsure whether your workspace is affected, or if a sync still fails after reconnecting, please contact our support team. We have also put proactive monitoring in place on Salesforce connection drops: our team is now alerted immediately if an integration loses its connection, so we can act before it impacts your data syncs. We will post a final update once we've confirmed stable behavior across all workspaces.

Salesforce connections have been lost. The data team is currently investigating the issue.