Skip to main content

Resolve

Resolve an incident when the problem is fixed. Oppex stops escalation, closes the incident, and notifies the service if it subscribes to resolutions.

Permissions

The person the incident is assigned to can always resolve it. Owner, Global Admin, and Workspace Admin: any incident. Admin: incidents on services they are an admin of, or whose escalation policy they belong to. Responder: incidents on services whose escalation policy they belong to.

Resolve an incident​

  1. In the Incidents list, find the incident, or open it to use its detail panel.
  2. Click Resolve. Oppex shows "Status updated to Resolved."

The incident's status changes to Resolved, and the timeline records who resolved it. You can also resolve from the email or the mobile app.

A resolved incident cannot be reopened

After you resolve an incident, it can no longer be acknowledged, snoozed, or changed. Oppex shows "Resolved incidents cannot be modified." If the problem returns, the next alert opens a new incident.

Resolve with a root cause analysis​

Your organization may require a root cause analysis (RCA) before an incident can be resolved. To turn this requirement on or off, contact Oppex support.

When an RCA is required, clicking Resolve opens the Submit RCA form:

  1. In Issue Summary, describe what went wrong. This field is required.
  2. In Root Cause, describe why it happened. This field is required.
  3. In Fix Status, select Permanent or Temporary.
  4. If you selected Temporary, enter a Ticket Link that starts with http:// or https://, and pick an ETA for Permanent Fix. Both are required for a temporary fix.
  5. Optional: Add Remarks, and click Attach file to add supporting files.
  6. Click Submit & Resolve. Oppex shows "RCA submitted and incident resolved successfully".

The RCA form filled in with an issue summary, a root cause, Fix Status set to Permanent, and remarks

FieldLimit
Issue Summary, Root CauseRequired. 2,000 characters each.
RemarksOptional. 10,000 characters.
Ticket LinkRequired for a temporary fix. An http:// or https:// link of 1,000 characters or fewer.
ETA for Permanent FixRequired for a temporary fix. Today or a later date.
Supporting FilesUp to 5 files of 5 MB each: PNG, JPG, WebP, PDF, DOCX, XLSX, or CSV.
Add or edit an RCA without resolving

Click ⋮, and then click Update RCA. The form saves the RCA only and does not resolve the incident. On a resolved incident, click Update RCA to edit its RCA.

What happens when you resolve​

  • Escalation stops, and nobody else is paged.
  • The service's notification emails and Slack channel receive a resolution update if the service subscribes to Resolved. The email names who resolved it and includes the comments, and the RCA when your organization requires one.
  • The incident's group closes, so the next matching alert opens a new incident.

FAQ

Can I resolve an incident that is not assigned to me?

Yes, if you belong to the escalation policy of the incident's service, administer the service, or have the Workspace Admin role or higher.

What happens if the same alert fires after I resolve the incident?

Oppex opens a new incident. The resolved incident keeps its own history and is not reopened.

Why can't I resolve from the mobile app?

Your organization requires an RCA, and the mobile app has no RCA form. Resolve the incident in the web app.

In this article

FAQ

Can I resolve an incident that is not assigned to me?

Yes, if you belong to the escalation policy of the incident's service, administer the service, or have the Workspace Admin role or higher.

What happens if the same alert fires after I resolve the incident?

Oppex opens a new incident. The resolved incident keeps its own history and is not reopened.

Why can't I resolve from the mobile app?

Your organization requires an RCA, and the mobile app has no RCA form. Resolve the incident in the web app.