Friday January 30, 2026

Salesforce Slack channel creation is now working properly after the deployment of the fix to the production environment. We're currently clearing cached channel data to fully restore functionality for Salesforce channels created during the incident. We apologize for the trouble, but appreciate you bearing with us as we work to get things back in order.

9:58 AM PST

The change has been rolled back and is now scheduled to be deployed to the production environment. We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

9:32 AM PST

The team has reverted the change and deployed it in a staging environment. We’ll share another update in 30 minutes or sooner as progress continues. Thank you for your patience while we work to resolve this issue.

8:57 AM PST

The teams have identified the issue as being caused by a recent code change. We're reverting the change. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.

8:25 AM PST

We're aware of an issue where users may notice Salesforce channels renamed with a "ZC:" or alternative prefix and can't see channel discussions. Additionally, canvases on these channels may only appear in the Files section instead of at the top of the affected channel. We're actively looking into this and will update as soon as we know more.

7:52 AM PST

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.

4:58 PM PST

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.

4:09 PM PST

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.

3:40 PM PST

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.

3:14 PM PST

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.

2:38 PM PST

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:15 PM PST