2026.03-preview
- Changed
Slack incident loop now requires explicit ack for sev-1 before suppressing repeat pages.
Previously an emoji reaction was enough to acknowledge a sev-1 page and stop the repeat loop. We have seen enough cases of a reaction being dropped accidentally — a finger slip, a bot adding an emoji — that we no longer treat reactions as sufficient for a sev-1.
sev-1 acknowledgement now requires either the /gs ack slash command or
clicking the Acknowledge button on the alert card. The command logs
which human acked, which is also useful during the post-incident review.
sev-2 and sev-3 are unchanged — an emoji reaction still acks a sev-2, and sev-3 does not loop at all.
- Affects
- Customers using the Slack integration for sev-1 paging. sev-2 and sev-3 behaviour is unchanged.
- Action required
- None for most teams. If you relied on a reaction-based ack for sev-1, switch to the `/gs ack` command — reactions still work for sev-2 and sev-3.
- Links