Skip to content

fix: restored automatic quota failover - #193

Merged
jacobcxdev merged 1 commit into
mainfrom
jacobcxdev/fix/automatic-quota-reroute
Sep 8, 2026
Merged

jacobcxdev merged 1 commit into
mainfrom
jacobcxdev/fix/automatic-quota-reroute

Conversation

@jacobcxdev

Copy link
Copy Markdown
Owner

After a successful Codex request, quota exhaustion could leak a 429 and leave later requests failing with bound_unresolved or turn_state_presence_mismatch. Portable requests now record the rejection and retry an eligible account within the same HTTP request, with a fixed retry budget.

Bound continuations retain their account and can probe recovered quota. Cross-account admission replaces old turn-state and response-anchor evidence, so stale account-specific state cannot reach the replacement. Exhausted pools retain the provider 429.

Validation: regression tests reproduce the failures before the fixes, including successful follow-up requests, soft limits, required continuity, all-account exhaustion, and absent replacement state. Full build, vet and race-test results recorded before publication.

- Retried portable requests after quota rejection without manual resubmission.
- Preserved bound quota probes and provider exhaustion responses.
- Replaced account-specific continuity evidence at admission.
- Added regression coverage for recovery and exhausted pools.
@jacobcxdev jacobcxdev self-assigned this Sep 8, 2026
@jacobcxdev
jacobcxdev merged commit 744049f into main Sep 8, 2026
11 of 12 checks passed
@jacobcxdev
jacobcxdev deleted the jacobcxdev/fix/automatic-quota-reroute branch September 8, 2026 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant