Thursday July 25, 2024
![](/img/v2/TableIncident.png)
Incident
Some users reporting issues loading channels & messages
![](/img/v2/DetailPageCheck.png)
Issue Summary:
On July 25, 2024, at around 6:55 AM PDT, we began investigating an issue where users were unable to load channels or messages on the web browser version of Slack. Affected users received a "REBA9A00D434" error code.
We traced this issue back to the functionality of a 3rd party connector, which caused performance problems. Users who experienced the error were able to resolve it by disabling the connector in their web browser.
2:17 PM PST
To resolve the issue some users experienced when attempting to load channels or messages in the web browser, please deactivate the 3rd party connector in your browser.
We will continue to work directly with affected users through support tickets. For any additional questions, please contact us at feedback@slack.com.
1:57 PM PST
Thank you for your patience while we looked into this issue. From our investigation, it looks like this is caused by a conflict with a 3rd party extension, namely the Harpa AI extension for Chrome.
https://chromewebstore.google.com/detail/harpa-ai-automation-agent/eanggfilgoajaocelnaflolkadkeghjp?pli=1
If you're using this extension, please disable it and confirm if you're able to access your channels as expected.
7:33 AM PST
Some users have reported encountering error REBA9A00D434 on the Chrome browser. We encourage users who encounter this error to try using Slack in an incognito window or disabling browser extensions until we know more. We’ll continue to provide updates as we know more.
7:15 AM PST
Features affected
Connectivity
Status
Incident
![](/img/v2/TableIncident.png)
Incident
Users unable to execute workflows via buttons
![](/img/v2/DetailPageCheck.png)
Issue summary:
From 11:46PM PDT on July 24, 2024 to 8:20 AM PDT on July 25, 2024, some users were unable to execute workflows by clicking buttons.
We determined that a recent code change to the workflow buttons caused unexpected errors, preventing them from being clickable by the user. We immediately reversed this code change, which restored functionality to affected workflow buttons.
4:51 PM PST
Users should no longer be experiencing any issues executing workflows via buttons. Thank you for your patience and apologies for any disruption to your workday.
8:35 AM PST
Users may be unable to execute a workflow via buttons. We're investigating this issue and are working to understand the situation further. We'll let you know as soon as we have more details to share.
7:59 AM PST
Features affected
Workflows
Status
Incident