Are component statuses reset after resolving an incident?

[Wes]

Hello! Had a quick question.

Should component statuses automatically be reset back to "Operational" after an incident resolves?

Let's say I had an incident that updated two components from "Operational" status to "Degraded performance". Are these components automatically reset back to "Operational" status once the incident is resolved, or would this require a follow-up scheduled incident?

Thank you!

[Robert]

Great question, Wes — this one trips up a lot of users the first time around!

By default, component statuses don’t automatically reset to Operational when an incident is marked as resolved. The logic here is to give teams control — sometimes an incident may be “resolved” from a communication standpoint, but the underlying components might still need validation, monitoring, or a staged recovery before being declared fully operational again.

If you want components to automatically switch back to Operational, you can configure that behavior manually or use automation rules (depending on your platform setup). Many teams actually prefer keeping it manual — it ensures accuracy and avoids situations where a status flips to Operational too early.

So in short: ✅ not automatic by default, ⚙️ can be automated if needed, and 🧠 manual review is often the safer route.

[Anthony Morais]

Hi @Wes 

According to the documentation for Statuspage:

Components on a status page can be updated independently or as part of incident workflows. 

However, there is no automatic behaviour documented that resets a component’s status back to “Operational” just because an incident is resolved. See the doc

The guide states: “The most common method of updating component statuses is by creating an incident, and changing the status of the affected components during the incident creation workflow.” 

Also: “Component status changes do not trigger notifications. Only incidents trigger subscriber notifications.

To summarize basically:

If you changed component statuses to something like Degraded performance during an incident, you will need to manually update the component status back to Operational after resolving the incident (or use an automation or API to do so).

You should verify your process: when your incident was resolved, did you also execute a component status change (manually or via webhook/API)? If not, the components will stay in the last status you set.

If you want automatic resets, you can build that via the Statuspage API or set up a webhook/integration that, upon “Incident resolved”, triggers a component status update to “Operational”.

Hope this helps!