Some escalations are running out of order when incidents repeat / re-trigger

Escalations

Operational

Resolved

We have deployed a fix for this issue. The incident was caused by the escalation step counter not resetting when a repeated incident was auto-resolved, causing subsequent triggers to resume from the last escalation step instead of restarting from step 0.

The fix is now live and escalations should start correctly for all repeated incidents going forward. If you continue to experience any issues, please reach out to our support team.

We are actively monitoring the situation. Thank you for your patience.

Mar 06, 2026 - 02:33PM (UTC)

Update

We have identified the root cause of this issue and we are actively working on a fix. We will post another update shortly with our progress.

Mar 06, 2026 - 01:02PM (UTC)

Identified

We identified an issue where repeated incidents were not restarting the escalation process correctly. When an incident triggered, escalated to step N , and later auto-resolved, a subsequent incident with the same conditions would resume alerting from step N instead of restarting from step 0 .

Thank you for bringing this to our attention, we are working closely on investigating and we will post updates as we learn about it more.

Mar 06, 2026 - 12:53PM (UTC)

Components affected

Escalations

Reported on

Fri, Mar 6, 2026 12:53 PM (UTC)

Resolved at

Fri, Mar 6, 2026 2:33 PM (UTC)

Friday Mar 06, 2026