Incident: Trouble Accessing Historical Messages With Custom Data Retention Policies Enabled

Timeline

1. 14 Sep · 22:31 UTC 🟡 Resolved rss

   We've completed restoring shared files for all remaining affected workspaces and restored and verified all affected data. If you still can't see previous content, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Thank you for your patience while we sorted out this issue.

2. 11 Sep · 15:53 UTC 🟡 Resolved rss

   We’ve completed message data restoration across affected teams and channels, and are now focused on restoring file shares which should be the last step towards resolution. We'll provide another update as soon as new information becomes available.

3. 09 Sep · 02:37 UTC 🟡 Investigating rss

   We've made further progress restoring message data across affected teams and channels, with most batches now complete. We've deployed a tool to correct thread reply links affected during the restore process and are running it now. Slack Connect message restoration is resuming production runs, with results being closely monitored.  We'll provide an update as soon as new information becomes available.

4. 04 Sep · 17:00 UTC 🟡 Resolved rss

   We’ve made further progress restoring messages, message edits, and shared files affected by this issue. We identified and resolved a technical limit that was slowing recovery for some accounts, and recovery for Slack Connect workspaces is now underway. Message edit restoration is nearing completion for affected workspaces. We’re continuing to validate restored data as recovery progresses.We’ll provide another update as significant progress is made.

5. 01 Sep · 22:51 UTC 🟡 Monitoring rss

   We continue to restore batches of messages, message edits, and shared files. Each batch requires careful planning, monitoring, and validation to ensure the affected messages are accurately restored. Custom retention processing remains re-enabled for affected active workspaces. Thank you for bearing with us while we continue to work through this complex and nuanced issue. More updates will come as restoration and validation progress.

6. 27 Aug · 18:58 UTC 🟡 Resolved rss

   We’re continuing our work to restore the remaining message data affected by this issue. We’ve made further progress across the recovery processes for messages, message edits, and shared files. Validation of the message-edit recovery process has identified additional adjustments needed before restoration proceeds, while preparation and validation for message recovery continue. We’ve also completed additional development work supporting shared-file restoration, including handling for shared channels.Custom retention processing has been re-enabled for affected active workspaces. We’ll continue to provide updates as restoration and validation progress.

7. 25 Aug · 20:55 UTC 🟡 Investigating rss

   We’re continuing our work to restore the remaining message data affected by this issue. Our teams have made progress developing and validating the recovery process for messages, message edits, and shared files. We’re addressing additional technical dependencies and completing validation before proceeding with the next stages of restoration.We’ll continue to provide updates as we make progress.

8. 20 Aug · 22:54 UTC 🟡 Investigating rss

   We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs.We will provide another update as additional information becomes available.

9. 20 Aug · 22:54 UTC 🟡 Investigating rss

   We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs.We will provide another update as additional information becomes available.