Chapter 11. When the Worker Goes Wrong
In this section
- Chapter 11. When the Worker Goes WrongHow to stop a failing AI Worker, read its task record, check that a run really worked, find which of five causes a failure comes from, and fix it so the fix lasts, on Claude or ChatGPT.
- 11.1 Stop first, then read the recordWhat to do first when an AI Worker's run goes wrong: stop it, read its record and check what changed, on Claude and ChatGPT.
- 11.2 Ran is not the same as workedWhy a run that finished does not prove the work succeeded, and how to give every recurring job a success signal.
- 11.3 Where a failure lives: five causes, cheapest firstThe five places a failure can come from, how to check them cheapest first, and what each check can and cannot prove.
- 11.4 Usage and limitsHow usage limits and a shared allowance can stop a recurring job, and how to plan and check usage on Claude and on ChatGPT.
- 11.5 Fix the brief, the inputs or the permissionsHow to fix a known cause by changing the brief, the inputs or the permissions, one change at a time, and test the fix.
- 11.6 Make the fix stick, and optimize from feedbackHow to move a fix out of a chat so it lasts for everyone, and use feedback and a baseline to improve the work.
- 11.7 The details on today's toolsWhat Anthropic's and OpenAI's own pages say about task records, scheduled runs, usage and limits, and what two open-source tools add.
- Lab 11: where each failure livesChapter 11's lab: find where each of the AP Worker's failed runs lives, from its task record, before changing anything. Stop and hold what the runs left, fix one lever at a time on the input that failed, give each repeated correction a lasting home, check each task against its own key, and run the same week again on the fixed Role Contract.
- Check yourselfRecall and practice for the whole chapter: the flashcards, and a final quiz round from all seven concepts.