What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments

Having problems with Salesforce now? Check the current status

Updates (13)

12-11-2026 19:13
feature Service Disruption (20004594)
Agentforce connections from the mobile Software Development Kit (SDK) and Life Sciences iPad integrations are now working as expected. We restored the previous authentication configuration on the affected production instances, and the impact ended at 17:21 UTC on November 12. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Salesforce ↗
12-11-2026 18:30
feature Service Disruption (20004594)
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
Salesforce ↗
12-11-2026 18:28
feature Service Disruption (20004594)
We've confirmed in test environments that the connection errors clear after the change, and automated checks there passed. We've started applying the change to the affected production instances, which we expect to take less than an hour. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 18:11
feature Service Disruption (20004594)
The corrected change has been built and is being deployed to the test environments. Early monitoring shows no new connection errors. We continue to monitor the deployment progress. Once verified and confirmed, we'll apply the change to affected production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 17:47
feature Service Disruption (20004594)
We've prepared a change that restores the previous authentication configuration and are building it for deployment. We'll deploy it to a test environment first to confirm the connection errors clear, then apply it to affected production instances. Customers using the mobile Software Development Kit (SDK) and Life Sciences iPad integrations may still be unable to connect to Agentforce. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 17:17
feature Service Disruption (20004594)
We've narrowed the trigger to a recently applied authentication configuration that stopped passing the required identifier to Agentforce. We're restoring the previous configuration in a test environment to confirm it resolves the connection errors before applying it to affected production instances. Customers using the mobile Software Development Kit (SDK) and Life Sciences iPad integrations may still be unable to connect to Agentforce. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 16:53
feature Service Disruption (20004594)
We've identified that Agentforce isn't receiving a required identifier from connection requests made by the mobile Software Development Kit (SDK) and Life Sciences iPad integrations. We believe a recent change removed the identifier. We're preparing a fix that can restore a previously working configuration. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 16:31
feature Service Disruption (20004594)
We're continuing to assess changes within the setup process and how these correlate to the impact. Customers using the mobile Software Development Kit (SDK) and Life Sciences iPad integrations may still be unable to connect to Agentforce. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 16:05
feature Service Disruption (20004594)
We're still working to understand the recently identified update processes' role in the continued errors being observed and any changes in its process that may be contributing to the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 15:36
feature Service Disruption (20004594)
Our investigation into the Agentforce connection errors affecting mobile apps shows they began as early as 03:00 UTC on November 11, before the suspected release. We've widened the investigation and identified a separate update process that ran around the time the errors began, and we're working to understand its role in the errors. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 15:07
feature Service Disruption (20004594)
We've rolled back a recent release on one affected instance and are monitoring the results. Errors continue on that instance, so we're investigating whether the release is the only cause. Customers using the mobile SDK and Life Sciences iPad integrations may still be unable to connect to Agentforce. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 14:37
feature Service Disruption (20004594)
We've begun rolling back the configuration change, starting with a single test instance to confirm that it resolves the issue before proceeding with the remaining affected instances. We expect the rollback to take approximately 40 minutes per instance. Customers may continue to experience connection errors until the rollback is complete. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗
12-11-2026 14:29
feature Service Disruption (20004594)
We're aware of an issue affecting Agentforce that is preventing customers from connecting to Agentforce agents through the mobile SDK and the Life Sciences iPad application. Affected customers may encounter errors related to missing sessions or tenant keys. The issue began on November 11 at 16:15 UTC. Our investigation has identified a recent release as a potential cause, and we're coordinating a rollback to help restore service. As our investigation has progressed, we've confirmed that the issue affects more instances than initially identified. We've updated the incident posting to include these additional instances, and customers on the affected instances will now receive ongoing communications about this incident. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Salesforce ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Salesforce's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.