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.team:panaversity
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.team:panaversity
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.team:panaversity
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.team:panaversity
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.team:panaversity
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.team:panaversity
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.team:panaversity
11.7 The details on both AI vendorsWhat Anthropic's and OpenAI's own pages said on 8 October 2026 about task records, scheduled runs, usage and limits.team:panaversity
Lab 11: diagnose and fix four failed runsChapter 11's lab: diagnose four failed runs of Brightline's AP Worker from their task records, fix them, and move the fixes into its setup.team:panaversity
Check yourselfRecall and practice for the whole chapter: the flashcards, and a final quiz round from all seven concepts.team:panaversity