Incident Troubleshooting
Use this page when incident creation, updates, metrics, or postmortems do not behave as expected.
You cannot start a manual incident
Check whether you already have an enabled incident schema.
If not, create one first. See Incident Schema for Manual Incident Creation.
Start incident opens, but the form is missing useful defaults
The selected incident schema may not define defaults for:
- title
- priority
- description
- labels
Review the incident schema if the team expects those values to be prefilled.
Join the incident is disabled or already shows Joined
If the button already shows Joined, your user is already part of the incident response.
If you expected to join but cannot, refresh the incident and check whether someone already added you through the alert-driven response path.
Priority changes do not produce the workflow you expected
Check:
- the incident priority actually changed
- any related Incident Actions use the
priority_changedtrigger - any related conditions match the incident fields you expect
Postmortem cannot be edited
The incident must be resolved or closed before the Postmortem tab becomes editable.
If the incident is still active, that is expected behavior.
Incident Actions did not run
Check:
- the action is enabled
- the trigger event is the one that actually happened
- schema scope matches the incident
- conditions match the incident context
Then open History on the incident details page and confirm whether an action execution was recorded.