> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.
# Resolve and close
> How to close an incident's loop, manually or automatically.
## 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.
How aciona.me correlates alerts and what each tool requires.
The **generic webhook does not auto-resolve**. It always opens or aggregates incidents; resolution has to happen in the dashboard. If you need auto-resolution, use your tool's dedicated source type.
## Close
Closing (`closed`) is the administrative step after resolution: the incident leaves current operations and becomes history.
Not every team uses both steps. A common flow is:
* **Resolve** as soon as the service is back to normal.
* **Close** after review — once the team has confirmed the cause or recorded the learning.
## Reopened? No.
aciona.me does not reopen resolved or closed incidents. If the problem comes back, the new alert creates a **new incident**. 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.