Slack incident

Events errors related to Salesforce Automation application

Minor Resolved View vendor source →

Slack experienced a minor incident on January 30, 2026 affecting Apps/Integrations/APIs, lasting 2h 43m. The incident has been resolved; the full update timeline is below.

Started
Jan 30, 2026, 10:15 PM UTC
Resolved
Jan 31, 2026, 12:58 AM UTC
Duration
2h 43m
Detected by Pingoru
Jan 30, 2026, 10:15 PM UTC

Affected components

Apps/Integrations/APIs

Update timeline

  1. investigating Jan 30, 2026, 10:15 PM UTC

    We're investigating a new incident. Current impact to end users: Users may experience failures in events receiving the error "dispatch-unknown-error"We'll provide an update within 30 minutes, including further details on current actions being taken.

  2. resolved Jan 30, 2026, 10:38 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: users may be experiencing mTLS errors. We are working to identify the probable cause and alleviate the problem.We'll provide another update in 30 minutes until impact is resolved for all users.

  3. resolved Jan 30, 2026, 11:14 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: The team is reverting a TLS certificate rotation deployed this morning to restore event and slash command functionality for legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

  4. resolved Jan 30, 2026, 11:40 PM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: We are currently reverting a TLS certificate rotation that caused authentication failures and are re-enabling events for affected legacy Salesforce apps to restore full functionality.We'll provide another update in 30 minutes until impact is resolved for all users.

  5. resolved Jan 31, 2026, 12:09 AM UTC

    Our work on this issue is still ongoing. Current status and actions being taken: Service restoration is underway with 50% of availability zones recovered; we have successfully reverted the TLS certificate and are manually restarting services to restore event and slash command functionality for all legacy Salesforce 1.0 apps.We'll provide another update in 30 minutes until impact is resolved for all users.

  6. resolved Jan 31, 2026, 12:58 AM UTC

    This issue is now resolved for all users. Current status and recent actions taken: We have successfully reverted a TLS certificate that caused authentication failures and re-enabled events for affected legacy Salesforce apps to restore full functionality.Previous impact to end users: Users may have experienced mTLS errors.Required resolution steps: No steps required.We apologize for any disruptions to your day.