FIELD NOTE / TIKTOK
Kill the worker after two sends.
The short film, the complete written thought, and the evidence behind it.
The TikTok conversation link will follow its public release.
Kill the worker after two sends.
Video caption
Kill the worker after two sends. A and B may finish late. Pass only with correct per-group recovery. Narration uses Eric's authorized AI voice clone. #EricFieldNotes
Full written post / accessibility read
In a disposable fixture, an agent dispatches a fleet move to two host groups. Stop its process before the last acknowledgement. Now give a new worker the recovery journal.
If the resumer issues a fresh fleet command, the first two groups can complete under the old operation while the new one changes them again. The summary cannot settle the ambiguity.
The journal lists target groups and dispatch identities. Query A and B, mark any still unknown, and send only work that the protected plan proves was never dispatched.
Test partial fanout and late completion before giving an agent fleet scope. Require no duplicate effect, an explicit unknown state and an owner for a branch that misses its deadline.
#EricFieldNotes
Four-beat scene transcript
1. Kill the worker after two sends.
In a disposable fixture, an agent dispatches a fleet move to two host groups. Stop its process before the last acknowledgement. Now give a new worker the recovery journal.
Visual: Can the resumer tell which groups were touched?
2. The dangerous answer is retry all.
If the resumer issues a fresh fleet command, the first two groups can complete under the old operation while the new one changes them again. The summary cannot settle the ambiguity.
Visual: A and B may finish late.
3. Inspect each branch by ID.
The journal lists target groups and dispatch identities. Query A and B, mark any still unknown, and send only work that the protected plan proves was never dispatched.
Visual: Do not touch a group until its effect is classified.
4. Rehearse the interruption.
Test partial fanout and late completion before giving an agent fleet scope. Require no duplicate effect, an explicit unknown state and an owner for a branch that misses its deadline.
Visual: Pass only with correct per-group recovery.
Research and claim limits
- AWS Step Functions redrive (S214)
- Temporal Child Workflows (S216)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.