Resolved after 3 hours 21 minutes, affecting Salesforce Inbound Data Integration and Salesforce Outbound Data Integration and 1 more, on September 16, 2026.
Action required: Re-authorization of the integration user Salesforce has confirmed that the root cause of this incident has been resolved. To restore the flow of data between Backstory and Salesforce, the following action is required on your end: Re-authorize the Backstory<>Salesforce integration user.
Affected components
Update timeline
- monitoring Sep 16, 2026, 04:25 PM UTC
We're aware of an ongoing Salesforce incident that may be affecting Backstory's performance. We're monitoring the situation closely, and the Backstory team will be in touch directly if customer action is required.
- monitoring Sep 16, 2026, 05:02 PM UTC
We don't have new information to share at this time. The Salesforce incident remains ongoing and may continue to affect Backstory's performance. Our team is still monitoring the situation closely, and we'll post another update as soon as anything changes. As before, the Backstory team will be in touch directly if any customer action is required.
- monitoring Sep 16, 2026, 06:07 PM UTC
We don't have new information to share at this time. The Salesforce incident remains ongoing and may continue to affect Backstory's performance. Our team is still monitoring the situation closely, and we'll post another update as soon as anything changes.
- resolved Sep 16, 2026, 07:46 PM UTC
Action required: Re-authorization of the integration user Salesforce has confirmed that the root cause of this incident has been resolved. To restore the flow of data between Backstory and Salesforce, the following action is required on your end: Re-authorize the Backstory<>Salesforce integration user.
Your product runs on more than Backstory
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services