# Successful call retried twice

Injected failure: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

Failure mode `retry_twice` of the CommitLayer failure matrix, on all 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 |
|---|---|---|---|---|
| Refund a customer | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 payments.refund_created effect(s) observed within 10m |
| Cancel a subscription | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 crm.subscription_cancelled effect(s) observed within 10m |
| Change a shipping address | success | PASS | PASS / PASS | all 3 expected effects observed within 10m; preconditions, limits and prohibitions respected |
| Approve a discount | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 orders.discount_applied effect(s) observed within 10m |
| Close a support case | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 tickets.ticket_closed effect(s) observed within 10m |
| Send a payout | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 payments.payout_created effect(s) observed within 10m |
| Deploy a service | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 platform.deploy_created effect(s) observed within 10m |
| Place a trade | success | FAIL | PASS / FAIL | forbidden effect observed: more than 1 broker.order_created effect(s) observed within 10m |

## Refund a customer

Scenario `refund/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /tickets/tick_1`: 200
- `GET /orders/order_1001`: 200
- `POST /payments/refunds`: timeout (injected: lost_response)
- `POST /payments/refunds`: timeout (injected: lost_response)
- `POST /payments/refunds`: 200
- `POST /orders/order_1001/status`: 200
- `POST /crm/notes`: 200
- `POST /tickets/notify`: 200

### What the systems of record showed

Records written after the action:

- payments `refund_created` on order_1001 (amount=180, currency=USD)
- payments `refund_created` on order_1001 (amount=180, currency=USD)
- payments `refund_created` on order_1001 (amount=180, currency=USD)
- orders `order_status_changed` on order_1001 (status=refunded)
- crm `note_added` on order_1001 (author=lab-agent, text=Refunded 180.0 USD per customer request)
- tickets `customer_notified` on order_1001 (channel=email)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate refund.

### The verdict and why

FAIL — forbidden effect observed: more than 1 payments.refund_created effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 payments.refund_created effect(s) observed within 10m

## Cancel a subscription

Scenario `cancel/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /crm/subscriptions/sub_1`: 200
- `POST /crm/subscriptions/sub_1/cancel`: timeout (injected: lost_response)
- `POST /crm/subscriptions/sub_1/cancel`: timeout (injected: lost_response)
- `POST /crm/subscriptions/sub_1/cancel`: 200
- `POST /payments/billing/stop`: 200
- `POST /tickets/notify`: 200

### What the systems of record showed

Records written after the action:

- crm `subscription_cancelled` on sub_1 (plan=pro)
- crm `subscription_cancelled` on sub_1 (plan=pro)
- crm `subscription_cancelled` on sub_1 (plan=pro)
- payments `billing_stopped` on sub_1
- tickets `customer_notified` on sub_1 (channel=email)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate cancellation.

### The verdict and why

FAIL — forbidden effect observed: more than 1 crm.subscription_cancelled effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 crm.subscription_cancelled effect(s) observed within 10m

## Change a shipping address

Scenario `address/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /orders/order_1001`: 200
- `POST /orders/order_1001/address`: timeout (injected: lost_response)
- `POST /orders/order_1001/address`: timeout (injected: lost_response)
- `POST /orders/order_1001/address`: 200
- `POST /crm/notes`: 200
- `POST /tickets/notify`: 200

### What the systems of record showed

Records written after the action:

- orders `address_updated` on order_1001 (address=22 New Street, Lyon)
- orders `address_updated` on order_1001 (address=22 New Street, Lyon)
- orders `address_updated` on order_1001 (address=22 New Street, Lyon)
- crm `note_added` on order_1001 (author=lab-agent, text=Shipping address changed to 22 New Street, Lyon)
- tickets `customer_notified` on order_1001 (channel=email)

The oracle, reading the databases directly: outcome PASS, policy PASS.

### The verdict and why

PASS — all 3 expected effects observed within 10m; preconditions, limits and prohibitions respected (outcome PASS, policy PASS).

## Approve a discount

Scenario `discount/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /orders/order_1004`: 200
- `POST /orders/order_1004/discount`: timeout (injected: lost_response)
- `POST /orders/order_1004/discount`: timeout (injected: lost_response)
- `POST /orders/order_1004/discount`: 200
- `POST /crm/notes`: 200

### What the systems of record showed

Records written after the action:

- orders `discount_applied` on order_1004 (percent=15)
- orders `discount_applied` on order_1004 (percent=15)
- orders `discount_applied` on order_1004 (percent=15)
- crm `note_added` on order_1004 (author=lab-agent, text=Discount 15.0% approved)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate discount.

### The verdict and why

FAIL — forbidden effect observed: more than 1 orders.discount_applied effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 orders.discount_applied effect(s) observed within 10m

## Close a support case

Scenario `close/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /tickets/tick_1`: 200
- `POST /tickets/tick_1/close`: timeout (injected: lost_response)
- `POST /tickets/tick_1/close`: timeout (injected: lost_response)
- `POST /tickets/tick_1/close`: 200
- `POST /crm/notes`: 200
- `POST /tickets/notify`: 200

### What the systems of record showed

Records written after the action:

- tickets `ticket_closed` on tick_1 (order_id=order_1001)
- tickets `ticket_closed` on tick_1 (order_id=order_1001)
- tickets `ticket_closed` on tick_1 (order_id=order_1001)
- crm `note_added` on tick_1 (author=lab-agent, text=Case closed: answered)
- tickets `customer_notified` on tick_1 (channel=email, order_id=order_1001)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate close.

### The verdict and why

FAIL — forbidden effect observed: more than 1 tickets.ticket_closed effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 tickets.ticket_closed effect(s) observed within 10m

## Send a payout

Scenario `payout/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /ledger/accounts/acc_1`: 200
- `POST /payments/payouts`: timeout (injected: lost_response)
- `POST /payments/payouts`: timeout (injected: lost_response)
- `POST /payments/payouts`: 200
- `POST /ledger/accounts/acc_1/post`: 200
- `POST /crm/notes`: 200

### What the systems of record showed

Records written after the action:

- payments `payout_created` on acc_1 (amount=900, currency=USD, payout_id=po_acc_1_1)
- payments `payout_created` on acc_1 (amount=900, currency=USD, payout_id=po_acc_1_2)
- payments `payout_created` on acc_1 (amount=900, currency=USD, payout_id=po_acc_1_3)
- ledger `ledger_posted` on acc_1 (amount=900, balance=9100)
- crm `note_added` on acc_1 (author=lab-agent, text=Payout of 900.0 USD sent)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate payout.

### The verdict and why

FAIL — forbidden effect observed: more than 1 payments.payout_created effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 payments.payout_created effect(s) observed within 10m

## Deploy a service

Scenario `deploy/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /platform/services/svc_api`: 200
- `POST /platform/services/svc_api/deploy`: timeout (injected: lost_response)
- `POST /platform/services/svc_api/deploy`: timeout (injected: lost_response)
- `POST /platform/services/svc_api/deploy`: 200
- `POST /platform/services/svc_api/healthcheck`: 200
- `POST /crm/notes`: 200

### What the systems of record showed

Records written after the action:

- platform `deploy_created` on svc_api (version=1.5.0, environment=production)
- platform `deploy_created` on svc_api (version=1.5.0, environment=production)
- platform `deploy_created` on svc_api (version=1.5.0, environment=production)
- platform `health_check` on svc_api (status=healthy, version=1.5.0)
- crm `note_added` on svc_api (author=lab-agent, text=Deployed 1.5.0 to production)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate deploy.

### The verdict and why

FAIL — forbidden effect observed: more than 1 platform.deploy_created effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 platform.deploy_created effect(s) observed within 10m

## Place a trade

Scenario `trade/retry_twice`: agent retries a successful call twice. The primary write succeeds but the agent repeats it (no idempotency key).

### What the agent reported

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

- `GET /broker/products/TSLA-USD`: 200
- `POST /broker/orders`: timeout (injected: lost_response)
- `POST /broker/orders`: timeout (injected: lost_response)
- `POST /broker/orders`: 200
- `GET /broker/orders/ord_TSLA-USD_3`: 200
- `POST /crm/notes`: 200

### What the systems of record showed

Records written after the action:

- broker `order_created` on TSLA-USD (order_id=ord_TSLA-USD_1, side=BUY, quote_value=900, status=FILLED)
- broker `order_filled` on TSLA-USD (order_id=ord_TSLA-USD_1, side=BUY, filled_value=900, filled_size=3.4351145, average_filled_price=262)
- broker `order_created` on TSLA-USD (order_id=ord_TSLA-USD_2, side=BUY, quote_value=900, status=FILLED)
- broker `order_filled` on TSLA-USD (order_id=ord_TSLA-USD_2, side=BUY, filled_value=900, filled_size=3.4351145, average_filled_price=262)
- broker `order_created` on TSLA-USD (order_id=ord_TSLA-USD_3, side=BUY, quote_value=900, status=FILLED)
- broker `order_filled` on TSLA-USD (order_id=ord_TSLA-USD_3, side=BUY, filled_value=900, filled_size=3.4351145, average_filled_price=262)
- crm `note_added` on TSLA-USD (author=lab-agent, text=BUY 900.0 USD of TSLA-USD)

The oracle, reading the databases directly: outcome PASS, policy FAIL: duplicate order.

### The verdict and why

FAIL — forbidden effect observed: more than 1 broker.order_created effect(s) observed within 10m (outcome PASS, policy FAIL).

- forbidden effect, more than 1 broker.order_created effect(s) observed within 10m

## 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.

- [Refund a customer, Successful call retried twice](https://commitlayer.ai/lab?workflow=refund&failure=duplicate_execution)
- [Cancel a subscription, Successful call retried twice](https://commitlayer.ai/lab?workflow=cancel&failure=duplicate_execution)
- [Change a shipping address, Successful call retried twice](https://commitlayer.ai/lab?workflow=address&failure=duplicate_execution)
- [Approve a discount, Successful call retried twice](https://commitlayer.ai/lab?workflow=discount&failure=duplicate_execution)
- [Close a support case, Successful call retried twice](https://commitlayer.ai/lab?workflow=close&failure=duplicate_execution)
- [Send a payout, Successful call retried twice](https://commitlayer.ai/lab?workflow=payout&failure=duplicate_execution)
- [Deploy a service, Successful call retried twice](https://commitlayer.ai/lab?workflow=deploy&failure=duplicate_execution)
- [Place a trade, Successful call retried twice](https://commitlayer.ai/lab?workflow=trade&failure=duplicate_execution)

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

- [`refund/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Drefund%2Fretry_twice)
- [`cancel/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dcancel%2Fretry_twice)
- [`address/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Daddress%2Fretry_twice)
- [`discount/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Ddiscount%2Fretry_twice)
- [`close/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dclose%2Fretry_twice)
- [`payout/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dpayout%2Fretry_twice)
- [`deploy/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Ddeploy%2Fretry_twice)
- [`trade/retry_twice`](https://commitlayer.ai/login?intent=trial&tier=developer&next=%2Fapp%2Fsandbox%3Fscenario%3Dtrade%2Fretry_twice)
