Skip to main content

Resolve

Resolving marks that the problem is over. The incident moves to resolved, the time is recorded, and resolution notifications go out to the configured channels. Anyone allowed to act on incidents can resolve — you do not have to be the current owner.

Automatic resolution

When the originating tool sends the recovery event for the same alert, aciona.me resolves the correlated incident on its own. That is what stops incidents from staying open after the problem has already passed. It depends on two things:
  1. The tool must be configured to send recovery events. Each integration has its own switch — and forgetting it is the most common configuration mistake.
  2. The correlation identifier must be stable between the trigger and the recovery.

Grouping and auto-resolution

How aciona.me correlates alerts and what each tool requires.
Automatic resolution applies to any active state, including after someone acknowledged the incident or took responsibility for it. On the generic webhook, it happens when the source sends "status": "resolved" with the same externalId as the opening. See Automatic recovery.

Close

Closing (closed) is the administrative step after resolution: the incident leaves current operations and becomes history. You can close at any time after resolving. Owners and admins can also close an incident that is still open: it is resolved and closed at the same instant.

Automatic closure

Nobody needs to remember to close. A resolved incident closes by itself: The incident detail shows the scheduled time and the reason. If the time has passed and the status has not changed yet, it shows Closure pending — the closure happens within about a minute. Opening, viewing or refreshing the page does not postpone the deadline, and the automatic closure sends no notifications. On the timeline it appears as Incident closed automatically, with no person attached.

Reopened? No.

aciona.me does not reopen resolved or closed incidents — not even through escalation or assignment. If the problem comes back, the new alert creates a new incident, even while the previous one is still waiting for its automatic closure. That keeps response-time metrics honest and the timeline readable.
A recovery event arriving for an already-resolved or closed incident is silently ignored — no error, no change.