Long-running incidents

Long-running incidents are incidents with a duration of 7 days or more. The confirmation check frequency for these incidents are automatically scaled back after a certain amount of time. The following table describes the changes to confirmation check frequency schedule for long-running incidents.

Incident Duration	Change to Schedule
7 days	Set to 60 minutes
30 days	Set to 1440 minutes
60 days	Pause check
90 days	The underlying metric or metrics will automatically be paused and the incident will be resolved. For Agent, OnSight, Fabric, and SNMP heartbeat incidents, the corresponding metrics that depend on those will also be paused.

For example, if an incident has remained active for 7 days, the confirmation check frequency will be changed to 60 minutes, overriding the configured check frequency for the metric. Once the duration reaches 30 days, the frequency will be changed to 1440 minutes. After 60 days, confirmation checks will be paused.

Note: The frequency changes only apply to confirmation checks. Original checks will still be ran until the 60-day mark where further checks will be paused.