Resolving event-day incidents

Live Ops keeps open and resolved incidents beside the event-day timeline. When the issue is under control, choose Resolve on the incident. EventOps stamps the resolution time and resolver while keeping the original severity, report, reporter, and created time visible.

Resolution is intentionally not deletion. The muted, resolved entry remains part of the event history and recap, making it possible to review what happened after the event. Repeated resolution is a no-op; an already resolved incident cannot receive a second resolution stamp.

If the incident is still active, update the operational team through the normal event communication channel before resolving it. EventOps does not interpret Resolved as confirmation that every external stakeholder was notified.

Access and roles

Anyone who can read the event can see its incident history. Logging or resolving an incident requires event write access: Owner, Admin, Planner, and Coordinator have it for agency events; custom roles need events.write. Viewer access is read-only and may also be limited to explicitly assigned events.

See /help/logging-incidents for severity and creation.