Monday January 23, 2023

Issue summary: On January 23, 2023 from 12:41 PM to 1:15 PM PST, some customers may have experienced issues executing workflows. A planned upgrade to part of our infrastructure caused an unexpected spike in database load. Our load-balancing system kicked in automatically, restoring normal workflow functionality.

6:34 PM PST

We feel confident that affected users should no longer experience issues with workflows. Thank you for your patience while we looked into this.

3:12 PM PST

While we're still investigating, users may see signs of recovery and should be able to use workflows again. We will post the next update once we have more information to share. We apologize for the disruption.

2:38 PM PST

We're investigating the root cause and will continue to post updates every 30 minutes.

2:04 PM PST

Some users may be having issues loading workflows or having connection issues resulting in multiple workflow entries or failure to submit. We're investigating and will post an update shortly.

1:35 PM PST

Issue summary: On January 23, 2023 from around 12:41 PM to 1:15 PM PST, some customers may have experienced delays when opening channels and threads. We made a scheduled improvement to part of our infrastructure which inadvertently caused an increase in database load. Our automated recovery system intervened, balancing the load and resolving the issue for all affected customers.

6:32 PM PST

We're seeing signs of recovery and feel confident that this issue is now resolved. Affected users should be see normal rates of responsiveness when loading channels and threads. Thank you for your patience while we looked into this.

3:06 PM PST

A small percentage of users may notice a delayed response when loading channels and threads. We're currently investigating and will post updates as soon as possible.

2:34 PM PST

Issue Summary: From January 23, 2023 at 3:00 PM PST to January 24, 2023 at 7:02 AM PST some customers encountered an error when opening a workflow in a new window. We determined this issue was caused by a recent change to how Slack handles additional windows. This change was reverted and the issue was corrected.

8:08 AM PST

Customers should no longer be experiencing any trouble using workflows. Please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) in order for this fix to be reflected on your end. Apologies for the trouble today and thank you for your patience.

11:46 PM PST

We apologize for the trouble that some customers are encountering an error code when opening a workflow in a new window. We’re still actively investigating this issue. Thanks for bearing with us.

11:17 PM PST

We’re still investigating issues with workflows. Thanks for sticking with us as we continue to work towards a fix.

10:46 PM PST

Our investigation is still ongoing at this time and no additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble.

10:15 PM PST

We are continuing to investigate, but we don’t have any new information to share at this time. We'll be back with another update soon.

9:43 PM PST

We’re still actively investigating this issue. Thank you for your patience as we continue to work towards a resolution.

9:06 PM PST

Some users may be noticing an error code when attempting to open a workflow in a pop out window. We're investigating the situation and we'll let you know once we have more information to share.

8:28 PM PST