Click Acknowledge on an incident to stop escalation, claim ownership, and let teammates know you are on it.
Acknowledging Incidents
When an incident fires, LemWatch shows it in the Incidents queue with an Acknowledge button. Clicking it:
Marks the incident acknowledged with your name and a timestamp
Stops any further escalation steps from firing
Lets the rest of the team see somebody is already working it
Skips this incident in future escalation sweeps, so the engine doesn't waste cycles on it
Why this matters now
The notification engine now filters out incidents where acknowledged_at is set at query time. Before, an acked incident still loaded its policy, steps, and prior fires on every sweep — that N+1 work is gone. The practical effect: ack one-click silences the whole policy.
Re-opening
If you ack by mistake or the issue comes back:
Open the incident
Click Reopen (or clear the ack via the keyboard shortcut r)
Escalation resumes from the next step in the policy
Best practices
Ack as soon as you start investigating — don't wait until you've fixed it