Delayed Slack Trigger Processing

As of February 28, 03:28 UTC, Slack has resolved the issue affecting event delivery, and new events are now processing as expected.

However, Slack has confirmed that missed events from the outage between February 27, 02:15 UTC and February 28, 03:28 UTC will not be replayed. This means any Zap runs triggered by Slack events during this period were lost and cannot be recovered.

For more details, refer to Slack’s official status update:

https://slack-status.com/2025-02/d41e4bfd1ccae26a

We apologize for the disruption and appreciate your patience. If you need assistance adjusting your Zaps, please reach out to our support team.

https://zapier.com/help

We're seeing some reports of reduced delays in processing incoming webhooks from Slack. We will continue to monitor the situation and provide updates here.

We identified that the Slack incident caused missed triggers between February 26th 18:00 UTC and February 27th 6:30 UTC. 


While we’re now receiving webhooks from Slack again, we’re still seeing some delays in processing them.

We’re communicating with the Slack team to address these issues and understand if the missed triggers can be recovered.

We will continue to monitor and update this StatusPage within then next 24 hours. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

Slack is undergoing an incident right now (https://slack-status.com/2025-02/1b757d1d0f444c34) which is resulting in delayed Zap trigger processing for Zaps powered by Slack triggers.

Slack is undergoing an incident right now (https://slack-status.com/2025-02/1b757d1d0f444c34) which is resulting in delayed Zap trigger processing for Zaps powered by Slack triggers.