Resolved -
This incident has been resolved.
Mar 5, 20:48 UTC
Monitoring -
Slack has implemented a fix and we are seeing signs of recovery. We are continuing to monitor the situation.
Mar 5, 20:37 UTC
Update -
We believe this degradation is related to an upstream Slack integration issue. We’re working with Slack on mitigations and will provide updates. You can follow the upstream status page at https://slack-status.com/2026-03/e63ca9cc0d76539c
Mar 5, 19:16 UTC
Identified -
We are discussing with the upstream integration provider to identify the root cause.
Mar 5, 19:02 UTC
Investigating -
We are investigating reports of `@Cursor` from Slack not triggering Cloud Agents.
Mar 5, 18:36 UTC