The echoing reservation
A timeout turns one intended booking into two.
- 01 Identify
- 02 Repair
- 03 Replay
Your goal
Reserve exactly one fictional meeting pod for 14:00.
Tool contract
A timed-out write may have succeeded. reserve_pod supports an idempotency_key and lookup_by_key. Reusing a key returns the original reservation.
01 · CALL
reserve_pod({ time: "14:00", idempotency_key: "meet-7" })02 · RESULT
Network timeout. Server outcome unknown.03 · CALL
reserve_pod({ time: "14:00", idempotency_key: "meet-8" })04 · RESULT
{ reservation: "pod_B" } · Audit shows pod_A also reserved.WRITTEN SCENARIO · NO TOOLS EXECUTE
Inspect the trace
Enable JavaScript to choose a diagnosis and replay repairs. You can still read the scenario and tool contract.
Your practice, your choice.
Optional analytics is off.
Optional measurement counts fixed mission events. No choices, trace content, text or uploads are collected. Privacy details.