> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/platform/incidents-and-maintenance/statuses-lifecycle-and-side-effects.md). # Statuses lifecycle & side effects ### Incidents #### Lifecycle Below is the lifecycle of an incident. However, an incident can be created with the initial status of investigating, monitoring, or issue. To report incidents that have already been resolved, use the "retroactive" type. ```mermaid graph TD Investigating --> Monitoring Monitoring --> Issue Issue --> Resolved ``` #### Update types and their side effects Posting an update to an incident adds information to its timeline and gives you the option of notifying your subscribers. However, some update types also have side effects on the incident. * **De-escalate**: Will de-escalate a major incident to minor. * **Escalate**: Escalates a minor incident to major. * **Resolve**: Marks the incident as resolved. ### Maintenance #### Lifecycle Below is the lifecycle of a maintenance. The "monitoring" status is optional and not used automatically. To report a maintenance that has already started, use the "essential" update type. ```mermaid graph TD Scheduled --> Started Started --> Monitoring["Monitoring (optional)"] Monitoring --> Completed ``` #### Update types and their side effects Posting an update to a maintenance adds information to its timeline and gives you the option of notifying your subscribers. However, some update types also have side effects on the incident. * **Started**: Starts a planned maintenance immediately. Its end date won't be automatically adjusted; this will require editing the maintenance. * **Resolve**: Marks the maintenance as completed. * **Postponed**: This update does not have a side effect, so a manual editing of the maintenance will be needed to set the new start/end dates.