Date: 2026-08-28
The SKAN Codex account reached its five-hour rolling limit. At 08:29 UTC, authoritative telemetry showed:
AutoCoder nevertheless persisted both the capacity cooldown and next recovery probe as 2026-09-04 06:03 UTC.
Capacity deadline selection used the greatest value across both provider reset timestamps and the daily fallback, regardless of which window was exhausted. The available weekly window therefore extended a five-hour exhaustion by one week.
The account interface also reduced this known state to the generic text Codex capacity blocked, hiding the actual provider limit that caused the block.
AutoCoder/AutoCoder-Engine PR #2717:
The change passed formatting, focused requirement tests, and the full Rust suite: 247 library, 959 main, 68 Gitea MCP, and 16 Kubernetes MCP tests.
PRs #2719 and #2720 subsequently made the account status explain the authoritative cause from the typed provider windows:
5h usage limit reached;Weekly usage limit reached;5h and weekly usage limits reached;Codex capacity blocked only when no exhausted window can be identified.That change passed the full suite: 248 library, 964 main, 68 Gitea MCP, and 16 Kubernetes MCP tests.
The change does not bypass a real provider limit. SKAN remains unavailable until the primary window resets, then receives at most one atomic recovery probe. Other accounts retain independent capacity and queues.
PR #2717 merged as 760543d5efc3f5aa482013ce8dfeaded7b90446f. Kubernetes is running immutable backend image gitea.app.lan/autocoder/autocoder-engine:sha-760543d5efc3; the deployment and account workers are Ready with zero restarts.
After startup reconciliation, SKAN remained correctly capacity-blocked at primary usage 100%, but both its cooldown and next probe were repaired to 2026-08-28 11:03:02 UTC, the exhausted primary-window reset. The non-exhausted secondary reset remains 2026-09-04 06:03:02 UTC and no longer delays recovery.
The other exhausted account was likewise repaired to its primary reset at 2026-08-28 11:53:39 UTC. The consulting and work accounts were not capacity-blocked and continued processing independently.
PR #2720 merged as 6f4503870cbee896db821e9ce1e60ca3f3c861b3. Frontend image gitea.app.lan/autocoder/autocoder-engine-frontend:sha-6f4503870cbe rolled out Ready 1/1 with zero restarts. The deployed WASM contains the new five-hour and weekly status strings.