ProCargo · queues
The fix the AI got wrong
- ProblemBackground jobs took 5-10 s each.
- Wrong turnClaude Code proposed a fix that looked plausible. It was wrong.
- Found byTimed each stage of the job in the logs and inspected the job payloads in the jobs table.
- Real causesThree of them:
dispatchAfterResponselost jobs under PHP-FPM, the chain carried 192+ serialized jobs instead of IDs, and a cache lock deadlocked. - Result0.5-1 s per job, 10x faster.













