Skip to content
Reloqui Docs

Rollback & incident postmortem

Who: on-call, SRE, release managers. Goal: understand and record what happened after a release.

The workflow

Section titled “The workflow”
  1. An incident source (PagerDuty/Opsgenie) posts an event; Reloqui correlates it to the release in its window.
  2. Roll back the release with a reason — it moves to rolled_back and notifies your channels.
  3. The deployment.rolled_back evidence lowers the release’s confidence and raises an exception.
  4. Review the Release 360 (incidents section + rollback lineage) and the operations note for the timeline.

Why it works

Section titled “Why it works”

Incidents are correlated but never scored — so you see “what happened after we shipped” without distorting “what shipped”. The rollback and its cause are part of the permanent record.