Acknowledging an Incident

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. Viewers cannot acknowledge incidents.

How to Acknowledge an Incident

From the Incidents List

  1. In the left sidebar, click Incidents.
  2. Find the incident you want to acknowledge (filter by Open status if needed).
  3. Click the incident to open it.
  4. Click Acknowledge at the top of the incident detail page.

The status badge updates to Acknowledged immediately and the acknowledgment timestamp is recorded.

From the Dashboard

  1. On the Dashboard, locate the Active Incidents section.
  2. Click the incident row to open the detail page.
  3. Click Acknowledge.

What Acknowledging Does (and Doesn't Do)

Does:

  • Changes incident status from Open to Acknowledged
  • Records the time of acknowledgment
  • Signals to your team that someone is investigating

Does not:

  • Stop PulseAPI from checking the endpoint — checks continue on the normal schedule
  • Send a notification to your team (no acknowledgment notification is sent)
  • Prevent auto-resolution — the incident will still auto-resolve when checks pass again
  • Require any additional input — there is no required note or reason field

Why Acknowledge an Incident?

Acknowledging is most useful when you have multiple team members watching the same dashboard. It prevents two people from investigating the same incident simultaneously without knowing about each other.

It also gives you a clean record in your incident history: you can see exactly when the incident was detected, when someone picked it up, and when it was resolved.

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

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

    • Incident Lifecycle: Open → Acknowledged → Resolved

      Every incident in PulseAPI moves through three statuses: Open, Acknowledged, and Resolved. This article explains what each status means, who can change it, and what notifications are sent at each transition. Status Overview Open → Acknowledged → ...

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