AutoCoder Engine workers appeared idle because the scheduler had no queued/running tasks after a Codex usage-limit cooldown. Investigation showed the worker pods were healthy, but cooldown state could be applied to the wrong auth slot because the cooldown query used a different account order than auth-slot selection.
active_account_cooldowns() orders enabled accounts by pay_as_you_go ASC, created_at ASC, id ASC, matching auth-slot and runner-limit ordering.main.474232f.gitea.app.lan/autocoder/autocoder-engine:sha-94c6fe5709b6.708 completed successfully at 2026-05-14 15:03 UTC.deployment/autocoder-engine rolled out successfully.5 running and 3 queued shortly after rollout.The newer deployed SHA 94c6fe5709b6 is a graph-refresh merge on top of the cooldown fix and contains commit 474232f.