Friday January 30, 2026

This issue is now resolved. 

• Current status and recent actions taken: The change has been rolled back and most channels are restored.
• Scope: A small number of users may have noticed Salesforce channels renamed with a "ZC:" or alternative prefix and could not see channel discussions.
• Required resolution steps: No additional steps are necessary.

We apologize for the disruptions to your business.

9:53 AM PST

Salesforce Slack channel creation remains stable and operational. We are actively restoring functionality for the impacted Salesforce channels.
Users may need to reload their Slack clients to see the restored features.

We apologize for the trouble and appreciate your patience as we complete the restoration process.

6:54 PM PST

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