Tuesday July 15, 2025

From Monday, July 14, 2025 at 3:42 PM PDT to Tuesday, July 15, 2025 at 2:24 PM PDT, some users experienced an issue with custom apps relying on Block Kit elements such as: dropdown or multi-select menus in Slack. When accessing affected fields, users may have encountered a "Nothing could be found." message or empty values.

When reviewing additional app logging through your developer tools, an "invalid_argument" (or similar) error may have also been present.

A recent code change related to improvements around Slack Block Kit introduced an issue with the backend processing of field values. This led to dropdown & affected menus not returning proper information. We identified & reverted the problematic code, resolving the issue for users. This required affected users to refresh their Slack client (Cmd/Ctrl + Shift + R) to capture the fix.

We later determined that the clients were not picking up this fix immediately, causing continued spikes of errors. This led us to reinstate our incident response processes while we implemented a permanent fix, allowing affected clients to receive the corrected code.

10:44 AM PST

This issue is now resolved for all users.

• Current status and recent actions taken: We identified the problematic code and implemented a permanent forward fix, resolving the issue for all affected users. 
• Scope: A subset of users attempting to trigger custom app functions that rely on message elements such as dropdown menus.
• Previous impact to end users: Dropdown menus for some custom apps were returning incorrect results (or none at all).
• Required resolution steps: We previously suggested a refresh of your Slack app (Cmd/Ctrl + Shift + R), which is still encouraged, but not required to capture this fix.

We apologize for any disruptions to your day.

7:04 AM PST

Our work on this issue is still ongoing.

• Current status and actions being taken: We've identified the cause of the issue and are working to get a permanent fix out the door to affected users.

We'll be back with another update once the fix is fully out.

2:42 PM PST

We're seeing an increase in reports of this issue recurring for some users. We're investigating additional causes but wanted to share an update. Some users may still encounter trouble with interactive elements from custom apps such as dropdown menus in Slack.

• Current status and actions being taken: We're investigating new reports of this issue recurring for some users, even after a hard refresh.
• Estimated time to resolution: No known estimated time.
• Scope: A subset of custom apps that depend on interactive elements such as dropdown menus.
• Current impact to end users: Some users may see "Nothing could be found" or blank results when trying to select an item in a custom app form.
• Known workarounds: Users may continue trying to refresh their client (Cmd/Ctrl + Shift + R).

We appreciate your patience as we work to get things back in shape.

11:52 AM PST

This issue is now resolved for all users.

• Current status and recent actions taken: We reverted a recent change to block kit functionality, which triggered the issue.
• Scope: A subset of users building custom/third-party apps.
• Previous impact to end users: An "invalid argument error" would be logged in the app logs if the custom app relied on the block.suggestion API. Users would experience elements such as a select menu/dropdown not returning proper values, or the items would show blank. If you’re still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).

We apologize for any disruptions to your day.

7:18 AM PST

Our work on this issue is still ongoing.

• Current status and actions being taken: We've rolled back the change that caused the issue and verified the fix in our dev and test environments. If you’re still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We appreciate your patience as we work to resolve the issue.
  
  
  

6:25 AM PST

Some third-party apps may be experiencing connection issues. Users may receive an "invalid argument error" when using the block. suggestion API. We're investigating and will let you know as soon as we have more information to share. We appreciate your patience.

1:30 AM PST

Between Thursday, July 10, 2025, at around 9:36 AM PDT and Tuesday, July 15, 2025, at around 2:50 PM PDT, some users were unable to accept email invitations to join workspaces. This affected newly invited users to a workspace.

A recent feature toggle, intended to adjust a backend validation system, was enabled for a small subset of users. This introduced an unexpected mismatch that prevented the "Continue" button from functioning properly, leaving it in a non-actionable state.

We rolled back the feature toggle, resolving the issue for all affected users. Workspace invites sent via email now have an actionable "Continue" button.

8:54 AM PST

This issue is now resolved for all users.

• Current status and actions being taken: We identified and reverted a recent change that caused the issue. Invited users should no longer experience issues with accepting new invites to workspaces in Slack.

Thank you for your patience as we worked on resolving this issue. We apologize for how this may have affected you.

3:18 PM PST

Our work on this issue is still ongoing.

• Current status and actions being taken: Invited users may still encounter trouble accepting their invite to the workspace as the "Continue" button is not actionable.

We'll be back with another update once we have news to share.

2:51 PM PST

We're investigating a new incident.

• Current impact to end users: New users are experiencing trouble accepting new invites to workspaces in Slack, resulting in a greyed-out button that prevents the new user account from being created.

Thank you for your patience, and we will be back once we have a significant update.

1:42 PM PST