---
title: Acknowledge and resolve from the incidents list, and a timeline that shows every confirming check
description: Working through a morning's incidents meant opening each one in turn, and the timeline of the ones you opened was thin: a single "confirmation" row and a…
canonical: https://watchfor.io/changelog/2026-09-07-incidents-list-and-timeline
---

[All updates](/changelog/page/4#2026-09-07-incidents-list-and-timeline) ⚡ Improved Sep 7, 2026 · v 6.8.1

# Acknowledge and resolve from the incidents list, and a timeline that shows every confirming check

Working through a morning's incidents meant opening each one in turn, and the timeline of the ones you opened was thin: a single "confirmation" row and a "Confirmed & Active" stamp sitting at the moment the first check failed, minutes before anything was actually confirmed. The list now has the actions on it — Acknowledge and Resolve in the row menu, or tick several rows and do both in one go, with one confirmation for the batch. And the timeline lists each confirming check with its own time and a 1/3 → 2/3 → 3/3 counter, with Confirmed & Active at the moment confirmation finished.

Tick rows, and each bulk action says how many incidents it will touch.

Each confirming check gets its own row, and Confirmed & Active sits where confirmation finished.

## Acting from the list

- The ⋯ menu on each row now has Acknowledge (any member, on a firing incident) and Resolve… (owners and admins, on any open incident), next to View details.

- Tick several rows and open Bulk actions . Each action says how many incidents it will touch, such as Acknowledge (2 firing) or Resolve… (3 open) , so incidents in the selection that are already resolved are left alone.

- One confirmation covers the whole batch, and each incident still gets its own line in the [activity log](/docs/organization/activity-log).

- The same works on a monitor's own Incidents tab.

## A timeline you can read

The timeline now shows what really happened:

- Issue First Detected when the first check failed.

- One Prober Confirmation row for each confirming check, with its own time, the location it ran from, and a counter that climbs towards the monitor's confirmation threshold: 1/3, 2/3, 3/3.

- Incident Confirmed & Active when the last confirmation arrived.

## An example

Your API starts failing at 03:12:00. The first check is 1/3, a second location fails at 03:12:30 (2/3) and a third at 03:13:00 (3/3). The timeline now puts Confirmed & Active at 03:13:00, so when someone asks "how long until we knew?", the answer is on the page: one minute.

In the morning, four incidents from a flapping endpoint are still open. Tick them, choose Acknowledge (4 firing) so the team knows you have it, and resolve them in one go once it is fixed.

More in [Incidents](/docs/alerting/incidents#acting-from-the-list).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-07-incidents-list-and-timeline · Site guide: https://watchfor.io/llms.txt