Skip to main contentOverview
Alerts in Rootly progress through a finite state machine with four possible statuses: open, triggered, acknowledged, and resolved. An Alert’s Status determines an alert’s current lifecycle stage and what actions can be performed on it. The current status is stored in the rootly_alert_status field, which is visible in the alert’s payload.
.png?fit=max&auto=format&n=usuFKS3869pMrird&q=85&s=b822f5cddb15db20f81a14f12421245d)
Alert Status Definitions
open
An alert in open status has been created and has not been assigned a notification target. Alerts are created in open status by default, and can be resolved or escalated to a notification target (i.e., a User or Escalation Policy).
triggered
An alert in triggered status is actively sending notifications to assigned targets, and can be acknowledged or resolved. An Alert will enter triggered status when it is assigned a notification target. If an Alert’s Route, Source, or Payload specifies a notification target, it automatically transitions to triggered status when it is created.
acknowledged
An alert that has been acknowledged by a responder, indicating they are aware of and working on the issue. Alerts can only transition to acknowledged from triggered status. If an acknowledged alert times out or needs to be re-escalated, it can transition back to triggered status.
resolved
A terminal state indicating the alert has been resolved and no further action is required. An alert with resolved status can still be re-triggered via escalation, reverting it back to triggered status. 
