Live / Salesforce / Incident
Salesforce: Degradation: Agentforce (367 instances)
Salesforce · salesforce.comMinor incidentResolved2026-11-12 17:35 UTC
Public — what happened
Summary
Salesforce said some customers on 367 instances cannot connect to Agentforce agents through its mobile SDK and the Life Sciences iPad app, and may see errors about missing sessions or tenant keys. The company said the problem began on November 11, and later updates indicated it may have started as early as 03:00 UTC that day. After first pointing to a recent release, Salesforce said it narrowed the trigger to an authentication configuration change that stopped passing a required identifier to Agentforce. As of its 17:30 UTC update on November 12, the incident was not resolved: Salesforce said the fix had passed testing and was being applied to affected production instances, and that the number of impacted instances was narrower than first thought.
Timeline
- Started — 2026-11-12 13:16 UTC
- Investigating — 2026-11-12 13:29 UTC (12 updates)
- Resolved — 2026-11-12 17:35 UTC · 4h 19m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Salesforce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Salesforce: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Salesforce report →
More from Salesforce
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.