--- title: SRM incident states description: Incidents can be in a few different states depending on how they are acted on. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/service-reliability-management/sr-incident-states.html release: australia product: Service Reliability Management classification: service-reliability-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Service Reliability Management reference, Service Reliability Management, ITOM AIOps, IT Operations Management] --- # SRM incident states Incidents can be in a few different states depending on how they are acted on. An incident is created in SRM when a third-party monitoring tool has an event. Incidents can be manually created or assigned. Edit actions from the incident form using the state button in the form. Use the **Save** button in the form to keep any changes you've made. Changes to incidents in the list view are automatically saved.
| State | Description |
|---|---|
| New | State on incident creation. The incident is logged but not yet worked on. |
| In Progress | The incident is assigned being worked on. |
| On Hold | The responsibility for the incident shifts temporarily to another entity to provide further information, evidence, or a resolution. |
| Resolved | A satisfactory fix is provided for the incident to ensure that it does not occur again. |
| Closed | The incident is closed when it is confirmed that the incident is satisfactorily resolved. |
| Canceled | Incident was triaged but found to be a duplicate incident, an unnecessary incident, or not an incident at all.To reopen an incident. Select **New**. |