AppsStatus Page

Incident communication · Autessa Status Page

Smart component restore

When you resolve an incident, Autessa Status Page sets its components back to Operational for you, except any component that another open incident or maintenance window still affects. Those keep their status, and Status Admin tells you how many were kept, so closing one incident never hides another.

3 of 3 in Incident communication
Start free
Resolving "Delayed webhook deliveries"SAMPLE
  1. Resolved update posted
    Affected: API, Notifications. Restore box ticked.
  2. Other open events checked
    "Database upgrade" is in progress and affects API.
  3. Notifications → Operational
    Nothing else affects it.
  4. API stays Under maintenance
    Still affected by the open maintenance window.
  5. Confirmation
    "Update posted. 1 component(s) stay affected by another open event."

The problem it solves

Closing one outage should not erase another

Incidents overlap: the API has a problem while the database is under maintenance, or two unrelated issues hit the same service. A simple "resolve sets everything green" switch would tell customers all is well while something is still broken. Forgetting to reset components is just as bad: a red light that never goes away.

What you get

  • A "Set the affected components back to Operational" checkbox appears when you resolve, on by default.
  • Before restoring, it checks every other open incident and every maintenance window in progress.
  • Components still affected elsewhere keep their current status.
  • The confirmation says how many stayed: "1 component(s) stay affected by another open event."
  • The same check runs when maintenance is completed or canceled.
  • Starting maintenance sets its components to Under maintenance; reopening an incident reapplies its severities.

How it works

How does smart component restore work?

  1. Post the Resolved update

    On the incident's page in Status Admin, pick Resolved and write the closing message.

  2. Leave the box ticked

    "Set the affected components back to Operational" is on unless you turn it off.

  3. Overlaps are checked

    Status Page looks at every other open incident and maintenance in progress and notes which components they still affect.

  4. Only free components go green

    Everything else this incident touched goes back to Operational.

  5. You are told what stayed

    The confirmation names how many components stay affected by another open event.

Status Admin · Post an update
SAMPLE
Post an update
Customers see it on the status page right away.
Status
Resolved
Message
All delayed webhooks have been delivered and delivery times are back to normal.
Set the affected components back to Operational
Post update

Every option

When components change on their own

OptionWhat it does
Report an incidentEach affected component takes the severity you picked.
Resolve an incidentAffected components go back to Operational unless another open event still affects them (optional, on by default).
Reopen an incidentAffected components go back to their incident severities.
Maintenance startsAffected components show Under maintenance.
Maintenance completes or is canceledSame restore as resolving, with the same overlap check.
Edit detailsChanging the affected list does not change current statuses; use the Overview for that.

Permissions

Who can do what?

WhoCan
Staff in Status AdminChoose whether to restore components when ending an incident or maintenance.
VisitorsSee components go back to Operational only when nothing else is still affecting them.

Connected

How it connects to the rest of Status Page

FAQ

Questions about smart component restore

Do components reset automatically when an incident is resolved?

Yes, if you leave the restore box ticked. Components that another open incident or maintenance still affects keep their status.

What if I want to keep a component red after resolving?

Untick "Set the affected components back to Operational" before posting, or change the component on the Overview afterwards.

Does the same apply to maintenance?

Yes. When maintenance is completed or canceled, its components are restored with the same overlap check.

All systems operational

Put smart component restore on your status page

Autessa Status Page puts components back to Operational when an incident is resolved, but keeps any component that another open incident or maintenance still affects.

Start free

100% customizable, code and all

Make Autessa Status Page fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours