Why Didn't My Incident Auto-Resolve?

Why Didn't My Incident Auto-Resolve?

If your endpoint is back up and passing checks but the incident is still showing as open, work through this checklist to find the cause.

How Auto-Resolution Works

PulseAPI resolves an incident automatically when a configured number of consecutive successful checks passes after the failure. "Successful" means the check returned the expected status code within the timeout — not just that the endpoint responds.

Checklist

1. Are the checks actually passing now?

Go to the monitor's detail page and look at the Check History. If the most recent checks show Up status, checks are indeed passing.

If checks are still showing Failed, the endpoint isn't healthy yet — the incident won't auto-resolve until it is. Check the error messages to understand what's still failing.

2. Is the check returning the expected status code?

A check is only "successful" if it returns the monitor's configured Expected Status Code (default: 200). If the endpoint is back up but returning a different code (e.g., a redirect to a maintenance page that returns 302), it won't count as a success.

Check the Status Code column in the check history.

3. Has enough consecutive success happened?

Auto-resolution requires multiple consecutive successful checks in a row, not just one. The exact number depends on the alert rule configuration. If the endpoint is flapping (alternating between passing and failing), it may not accumulate enough consecutive successes.

Look at the check history — are the recent successes truly consecutive, or is there a mix of successes and failures?

4. Is the monitor paused?

A paused monitor doesn't run checks, so auto-resolution can't occur. Check if the monitor shows a Paused status badge and resume it if needed.

Resolving Manually

If you've confirmed the endpoint is healthy and you want to close the incident now, resolve it manually:

  1. Open the incident.
  2. Click Resolve.
  3. Add a root cause note (optional).
  4. Click Confirm Resolution.

See Resolving an Incident for step-by-step instructions.

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 — ...

    • Resolving an Incident

      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. ...

    • 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. ...

    • 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 ...

    • 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 ...