Update an RCA
Tool: oppex.incident.updateRCA
Replaces the root cause analysis (RCA) on an incident that already has one, for example when the permanent fix ships or the investigation finds a different cause. It does not change the incident's status.
What you provide
| Input | Required | Field in Oppex | Description |
|---|---|---|---|
| Incident ID | Yes | The incident whose RCA you are changing. | |
| Reason for alert | Yes | Issue Summary | What went wrong. |
| Action taken | Yes | Root Cause | The cause, and what you did about it. |
| Type of fix | Yes | Fix Status | Permanent or Temporary. |
| Ticket link | For a temporary fix | Ticket Link | A link starting with http:// or https://. |
| ETA for permanent fix | For a temporary fix | ETA for Permanent Fix | A date and time. |
| Additional notes | No | Remarks | Anything else worth recording. |
The same rules as Resolve with an RCA apply to each field. Every field you send replaces the value that was there, so include the fields you want to keep as well as the ones you are changing.
Example prompts
- "The permanent fix for the Hyperdrive Failure incident shipped today. Update its RCA to a permanent fix and keep the rest."
- "Update the RCA on the checkout latency incident: the root cause was a connection pool limit, not the missing index."
- "Add the ticket link https://tracker.example.com/OPS-311 to the RCA on incident cacgichh-efbg-jv3t1ufo."
Who can use it
The same people who can resolve with an RCA: the assignee, Workspace Admins and above for any incident, Service Admins for services they administer or whose policies include them, and Responders for services whose policies include them.
This tool only changes an existing RCA. If the incident has none, Oppex returns an error saying the incident has no RCA yet. To add the first RCA, the assistant uses Resolve with an RCA for an open incident, or Update an RCA by incident or external ID, which creates the RCA when it is missing.