Rollback Basics
This page explains how rollbacks work and how to use them safely.
What is rolled back
- Each apply captures a checkpoint (at minimum, the previous value of the field being changed).
- Rollback uses these checkpoints to restore the prior configuration. Not every change is reversible without impact; consult agent notes.
When to roll back
- A remediation causes unintended degradation or cost spike.
- A follow‑up change supersedes the applied change.
How to roll back
- Identify the automation in the UI or via the API (automation_id or run_id).
- Request a rollback via the UI or
POST /rollback/{automation_id}(may require approval depending on risk guardrails). - Monitor events; on success, the prior configuration is restored and an audit event is recorded.
Guardrails and approvals
- Rollbacks may be auto‑approved when risk policy allows (e.g.,
auto_approve_rollbacks: true). - Otherwise, they follow the same approval flow as applies.
Observability
- Rollback attempts and results are logged and metered similarly to applies.