# Unhealthy after the deploy

Injected failure: forbidden side effect. The deploy lands but the service comes up unhealthy; the health check records it.

Failure mode `unhealthy_after` of the CommitLayer failure matrix, on 1 of its 8 workflows. Each run below is the sandbox's scripted agent acting on the sandbox's fake systems of record under the injected failure, an oracle reading those systems' databases, and the verdict of engine 1.0.0 from the systems of record alone. The accounts, orders and amounts are the sandbox's and describe no real customer. Last changed 2026-11-13.

| Workflow | Agent reported | Oracle (policy) | CommitLayer (outcome / policy) | Why |
|---|---|---|---|---|
| Deploy a service | failure | FAIL | FAIL / FAIL | The service reported unhealthy after the deploy |

## Deploy a service

Scenario `deploy/unhealthy_after`: forbidden side effect. The deploy lands but the service comes up unhealthy; the health check records it.

### What the agent reported

The agent reported failure. Its calls, and what it saw come back:

- `GET /platform/services/svc_api`: 200
- `POST /platform/services/svc_api/deploy`: 200
- `POST /platform/services/svc_api/healthcheck`: 200 (injected: before)

Agent notes: tool error: health check after deploy: unhealthy.

### What the systems of record showed

Records written after the action:

- platform `deploy_created` on svc_api (version=1.5.0, environment=production)
- platform `health_check` on svc_api (status=unhealthy, version=1.5.0)

The oracle, reading the databases directly: outcome FAIL, policy FAIL: forbidden: unhealthy after deploy; missing platform.health_check; missing crm.note_added.

### The verdict and why

FAIL — The service reported unhealthy after the deploy (outcome FAIL, policy FAIL).

- expected effect, platform.health_check observed within 10m of the action where status=healthy: No healthy check after the deploy
- expected effect, crm.note_added observed within 10m of the action: No change note was added
- forbidden effect, platform.health_check observed within 10m of the action where status=unhealthy: The service reported unhealthy after the deploy

## Run it in the Failure Lab

The Failure Lab replays each run above: the agent's calls, the records the systems held and the verdict. No account is needed. The verdict comes from the production engine while you watch.

- [Deploy a service, Unhealthy after the deploy](https://commitlayer.ai/lab?workflow=deploy&failure=unhealthy_after)

The sandbox in the app runs the exact scenario in your own workspace, as a verified action:

- [`deploy/unhealthy_after`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Ddeploy%2Funhealthy_after)
