Monitors & detections

A little hindsight after an interruption

Save a private review, track follow-up actions and finalize the wording when your team is ready.

Reviewed

Let recovery settle first

Reviews are available on every plan once monitoring records recovery. An open interruption does not offer a review yet. Use its internal notes while the team is still responding. Pausing a monitor does not count as recovery.

  1. Open Incidents → Resolved and select the recovered interruption.
  2. Find A moment to look back and choose Start review.
  3. Write what you know in Summary, Impact, Cause or Lessons learned. Choose Save review draft.

A few facts are a good start

You can save a partially completed draft. Each field allows up to 4,000 characters of plain text; add context in at least one field. You can clear individual fields while keeping another nonempty. Line breaks are preserved, and HTML is displayed as text. The editor uses a conservative character limit for emoji and some other characters.

Summary: checkout was unavailable for part of the afternoon. Impact: some visitors could not complete their orders. Cause: a connection limit was reached, confirmed in the service logs. Lessons learned: check connection usage before the next release. These are fictional examples, not automatically generated conclusions.

Write only what the team can establish. Leave an uncertain cause blank or describe what is still unknown. UptimeOwl starts with empty fields and does not generate a cause or copy diagnostics into the review. Keep passwords, credentials and secret tokens out.

Keep the page calm, return when ready

The incident detail shows who last saved the private draft and when. Choose Read private draft to expand the four fields. Edit draft reopens the shared editor with your saved wording. Owners and admins need current Manage access to this monitor to save; viewers and read-only support visits can read a saved draft when they can view the incident.

If another teammate saves first, your editor reports that the draft changed and keeps your wording open. Copy anything you want to retain, close the editor, Refresh the incident and compare the latest draft before saving again. Retrying the same saved wording does not create another change. If a save succeeds but refreshing fails, the saved draft remains visible with a message asking you to Refresh.

One useful next step

Actions are available on every plan for recovered incidents with a saved review. Each action allows 1–240 characters of plain text on one line. Keep a checklist of up to 50 active actions, with at most 100 created over the life of a review. Removing an action does not reset the creation allowance.

Only active, verified workspace owners/admins with Manage access to this monitor can be selected as owners. Unassigned is welcome. The picker loads 20 eligible teammates at a time; More teammates loads the next page. Search applies to choices already loaded. Assigning someone does not grant access or send a notification.

Owners/admins with current Manage access can change or complete any action. Viewers and read-only support can read the checklist, with disabled completion controls. If an owner becomes unavailable, their saved name stays visible with no longer eligible. You can finish the action, clear its owner or choose another eligible teammate.

After an action is saved, the checklist remains open and shows its completion count. Conflicting edits or stale removal attempts are rejected; Refresh the incident before trying again. A retry after a lost response does not create another action.

Removal clears the action text and owner, leaving a small retry-safe record and a content-free workspace audit entry. Removed actions cannot be restored. Completion and reopening are recorded in workspace history without copying action wording. No notifications, Jira tasks, public updates or monitoring changes are triggered.

  1. Save a private review draft, then open Follow-up actions below Read private draft.
  2. Choose Add action. Write one clear step, optionally choose a teammate and select Save follow-up.
  3. Tick the checkbox when the step is complete. Untick it to reopen the action. Use the pencil to edit its wording or owner, or the trash icon to remove it after confirmation.

Put the wording on record

Finalization is available to owners/admins with current Manage access on a recovered incident with a saved review and a nonblank summary. It is an explicit private review step; monitor recovery does not finalize it automatically.

Open follow-up actions do not prevent finalization. The confirmation shows how many remain open, and you can continue to add, assign, edit, complete, reopen or remove follow-ups without reopening the review wording.

If another teammate changes the wording or review state while your confirmation is open, Refresh and review the latest wording before confirming again. Reopening advances the review revision, so an older editor cannot overwrite the reopened draft. Retrying a confirmation after a lost response does not duplicate the change or reverse a later reopening.

The private incident timeline records who finalized or reopened the review and when. Choose Earlier review changes for older entries. Workspace history also records the action without copying review text. Viewers and read-only support can read this history but cannot finalize or reopen.

  1. Review the saved wording and add a short Summary if it is still blank. The other fields can remain empty when facts are unknown.
  2. Choose Finalize review, read the confirmation and confirm. The wording becomes read-only.
  3. Choose Read private review to read it. The card shows who finalized it and when.
  4. If the wording needs another pass, choose Reopen review and confirm. Edit draft becomes available again.

Private reflection, separate from public communication

A review stays inside the private incident detail. It is not added to monitor lists, mobile Detections, public status pages, widgets, alerts or Jira issues. Saving does not acknowledge, assign, change severity, reopen monitoring or publish a public update. Public communication remains a separate reviewed publication step.

Keep a review as a working draft or explicitly finalize its wording. Reopening allows further edits to the current wording; previous text versions are not stored. Finalization and reopening leave metadata-only history, and workspace audit records changes without copying review text.

The review follows its incident’s permissions and history allowance. When the incident leaves your available history it is no longer visible. Deleting the incident removes its review. Ask your workspace owner if access has changed.

A HELPING WING

Let’s find your next step.

Open the chat in the corner to ask a question. Prefer email? Drop us a note and we’ll help you from there.

[email protected]