Resolving an incident closes it — the problem is fixed and the endpoint is healthy. Incidents can be resolved automatically by PulseAPI or manually by a team member.
Prerequisites: You must be a team Owner, Admin, or Member to resolve incidents. Viewers cannot resolve incidents.
Auto-Resolution
PulseAPI resolves incidents automatically when your monitor starts passing checks again after a failure. Specifically, once a configured number of consecutive successful checks occurs, PulseAPI:
- Updates the incident status to Resolved
- Records the resolution timestamp
- Sends a resolution notification to the channels assigned to the triggering alert rule
Auto-resolution happens without any action from your team. You'll receive a notification when it occurs.
Note: If an incident isn't auto-resolving, the most common cause is that failed checks are still occurring or that eval records are missing. See Why Didn't My Incident Auto-Resolve?.
Manual Resolution
You can resolve an incident at any time, even if your endpoint is still down. This is useful when:
- The incident was a false positive and no real fix was needed
- You've resolved the underlying problem and want to close the incident before auto-resolution kicks in
- Auto-resolution is not configured for this alert rule
Steps
- In the left sidebar, click Incidents.
- Click the open or acknowledged incident you want to close.
- Click Resolve at the top of the incident detail page.
- In the modal that appears, optionally enter a Root Cause note explaining what caused the incident and how it was fixed.
- Click Confirm Resolution.
The incident status updates to Resolved, the resolution timestamp is recorded, and a resolution notification is sent to your configured channels.
Adding a Root Cause Note
The root cause note is optional but recommended. It helps your team understand what happened — especially useful for:
- Post-incident reviews
- Identifying patterns across incidents
- Communicating status to other team members
The note appears on the incident detail page after resolution and is included in the incident's history.
What Happens After Resolution
- The incident moves to the Resolved tab in your Incidents list
- Incident duration (started → resolved) is calculated and displayed
- A resolution notification is sent to your channels
- If the same endpoint fails again later, a new incident is created — resolved incidents cannot be reopened
Related Articles
Still have questions? Contact support.
Related Articles
What Is an Incident?
An incident is PulseAPI's record of a problem with one of your monitors. This article explains what triggers an incident, what information it contains, and how it relates to alert rules. What Creates an Incident Incidents are created automatically — ...
Viewing Incident History
The Incidents page shows a full history of all incidents on your team — open, acknowledged, and resolved. This article explains how to navigate and filter the list. Opening the Incidents List In the left sidebar, click Incidents. Filtering Incidents ...
Acknowledging an Incident
Acknowledging an incident tells your team that someone is aware of the problem and actively working on it. It moves the incident from Open to Acknowledged status. Prerequisites: You must be a team Owner, Admin, or Member to acknowledge incidents. ...
Pulse AI Incident Analysis
Pulse AI automatically analyzes incidents and generates a summary of likely causes and recommended next steps. This article explains how it works, which plans include it, and how to use it. What Pulse AI Analyzes When an incident is created, Pulse AI ...
Key Concepts: Endpoints, Checks, Incidents, and Alerts
This article explains the four core building blocks of PulseAPI and how they work together. Understanding these concepts makes every other part of the product easier to use. Endpoint (Monitor) An endpoint is a URL you want PulseAPI to watch. In ...