Some Slack messages may have not been ingested from 14:00 UTC - 14:50 UTC

We're still in the process of backfilling any messages that Slack might not have sent to us, but unfortunately we cannot backfill missing events like the Plain bot having joined a new channel. If you're missing any new channels that you added during the 14:00 to 14:50 GMT window yesterday, please remove and re-add the bot to resolve the issue.

During a Slack outage: https://slack-status.com/2026-05/fe557ca05fdb64fa earlier today, Slack failed to send events for messages sent during 14:00 and 14:50 GMT. As a result, those messages were never ingested from Slack to Plain, as Plain relies on these events to know what, exactly, to ingest.

Unfortunately, Slack did not notify us of the dropped events in their incident comms — our earlier status page update was more optimistic than it should have been as a result.

With that said, we do have a clear path forward on a solution here. We are currently running a script to identify and backfill these missing messages to your Plain instance over the next 36 hours. We expect this to complete sooner but we are being conservative with our estimate.

Moreover, if one of your customers sends a threaded reply to one of the currently-missing messages, Plain will ingest both the new message as well as its parent.