Tuesday June 24, 2025

Summary

From June 20, 2025 at 2:00 PM PDT to June 24, 2025 at 8:00 AM PDT, a subset of users on iOS version 25.06.30 may have experienced unexpected behaviors when sending messages, specifically with thread replies in Slack. When attempting to send a thread reply, the message would inadvertently get posted to a previous thread within the same channel.

This was traced back to a recently enabled feature toggle, intended to improve message draft functionality, which introduced unexpected backend logic related to the message timestamp. This logic caused the affected replies to be incorrectly mapped to an earlier parent message within the same channel.

We rolled back the problematic feature toggle, resolving the issue for all affected users. We're improving the logic to reduce the likelihood of this reoccurring.

9:19 AM PST

Resolved

This issue is now resolved for all users.

• Current status and recent actions taken: We identified a recent feature toggle that introduced this unexpected behavior and have rolled it back.
• Scope: This issue only impacted users on iOS.
• Previous impact to end users: A subset of users on iOS may have experienced ‌unexpected behavior when trying to send a message, including thread replies. Affected thread replies were inadvertently posted as a reply to an unexpected thread within the same channel.
• Required resolution steps: Users may need to close and relaunch their Slack app.

We apologize for any disruptions to your day.

We've adjusted this post to provide additional clarity around user impact.

7:56 AM PST

Investigating

We're investigating a new incident.

• Current impact to end users: Some users on iOS are inconsistently experiencing unexpected behavior when trying to send a message, including thread replies. These messages are incorrectly posted to unexpected thread conversation.

We'll provide an update within 30 minutes including further details on current actions being taken.

7:37 AM PST