RobinBaker0512 · 21 Feb 2026, 03:29 UTC
Where does your program save that number relative to placing the puck and confirming the placement?
23 pointsAfter confirmed placement. Stop between placement and save leaves the old number. No recovery state recorded.
15 pointsSaving earlier just moves the uncertainty to an apparently used pocket which might still be empty; have the programmer retain the transfer stage and tray identity, then agree a recovery check for any physical result the stored state cannot establish, without automatically repeating the transfer.
20 pointsProgrammer added a pending transfer tied to the tray and pocket. Restart with pending work opens a recovery check. No automatic repeat. We are testing interrupted stages before releasing the job.
14 pointsInclude failure to save that pending state and failure to save completion, plus a different tray on restart; somebody covering the cell needs to recognise those cases without reconstructing your program.
9 pointsTests passed: failed pending save prevents dispatch; lost completion save retains pending recovery; different tray blocks continuation. Maintainer and cover operator completed the agreed physical checks without guessing the pocket. Handover accepted. Thanks for spotting the earlier-save trap.
5 pointsAnd keep those interrupted cases with the job's checks, so a later tidy-up doesn't quietly replace recovery with loading the last pocket number again.
14 pointsThis discussion is closed to new replies after six months without activity. Last activity: .