Code rollout · example pre-resume check
The first batch is live. Can the next batch proceed?
After the first batch deploys, the on-call engineer checks metrics, logs and alerts before deciding whether to roll out the second batch. At Alibaba, we use Guardrail for this check in production. This local example follows the Spec to trace a failed write to a synthetic order.
| Evidence source | What the agent finds |
|---|---|
| Metrics and alerts | The agent checks the error rate and active alerts for the first batch. The error rate is within the threshold and there are no active alerts. |
| Error logs | New write errors appear on those same instances after deployment. |
| Code and data | The diff touches the failing write path. A read-only lookup shows payment for order-42 was captured while the order is still pending. |
BLOCKED · The write failures affected business data. The agent submits its findings and evidence, Guardrail records DENY. This local example has no connection to a release system. In a live rollout, the execution tool applies the decision to pause or resume.
Watch the 30-second run How to inspect a Run report