--- title: X description: Sometimes you know an incident is over before the next check does. Owners and admins can now resolve an incident by hand. If the check is still failing it… canonical: https://watchfor.io/changelog/2026-06-24-manual-incident-resolve --- [All updates](/changelog/page/9#2026-06-24-manual-incident-resolve) ✨ New Jun 24, 2026 · v 3.1.7 # Resolve incidents manually Sometimes you know an incident is over before the next check does. Owners and admins can now resolve an incident by hand. If the check is still failing it simply re-opens, and the channels that were originally alerted are told who resolved it and why. Resolving asks for confirmation first. The false-positive option came later. ## How it works Owners and admins open the incident and click Resolve . A dialog asks you to confirm and explains what happens next. - The channels that were alerted get a message saying the incident was resolved by hand, and by whom. - The incident timeline and the activity log record it. - If the check is still failing, the incident simply opens again on the next confirmed failure. Resolving can't hide an outage. ## Resolve or acknowledge? - Acknowledge (any member) says "I'm on it". The incident stays open until it recovers. - Resolve (owners and admins) says "It's over". The incident closes now. ## Example Your domain's registration lapsed and you renewed it at 16:05. A domain monitor looks the domain up once a day, so its incident would stay open until tomorrow's check. You resolve it by hand, and the team channel gets the resolved message with your name straight away. Had the renewal not gone through, the next check would open the incident again. See [Manual resolve](/docs/alerting/resolving#manual-resolve). Since then, you can also [resolve from the incidents list](/changelog/2026-09-07-incidents-list-and-timeline), one row or a whole selection at a time. Share this update --- Canonical page: https://watchfor.io/changelog/2026-06-24-manual-incident-resolve · Site guide: https://watchfor.io/llms.txt