Salesforce incident

We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality re

Minor Resolved View vendor source →

Salesforce experienced a minor incident on September 8, 2026 affecting NA223 and USA1000 and 1 more component, lasting 3h 7m. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2026, 08:19 PM UTC
Resolved
Sep 08, 2026, 11:26 PM UTC
Duration
3h 7m
Detected by Pingoru
Sep 08, 2026, 08:19 PM UTC

Affected components

NA223USA1000USA1056USA1108USA1142USA718USA720USA730USA734USA740

Update timeline

  1. identified Sep 08, 2026, 08:19 PM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Sep 08, 2026, 08:28 PM UTC

    We’re investigating an issue affecting Agentforce session scoring and tagging functionality for a subset of customers. Our teams are actively working to identify the trigger and restore service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Sep 08, 2026, 08:58 PM UTC

    We’re continuing to investigate an issue affecting Agentforce session scoring and tagging for a subset of customers. Our teams are analyzing processing failures and reviewing affected customer environments to determine the trigger and identify a path to restore functionality. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring Sep 08, 2026, 09:37 PM UTC

    Our teams have narrowed the investigation to failures occurring during session processing and are working to identify a path to restore functionality. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

  5. monitoring Sep 08, 2026, 10:41 PM UTC

    We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.