Skip to content

fix: explain an unreachable ChatGPT backend as a connection failure - #697

Merged
EugeneTheDev merged 1 commit into
mainfrom
eugenethedev/ijai-5147-routing-discovery-failure
Oct 28, 2026
Merged

EugeneTheDev merged 1 commit into
mainfrom
eugenethedev/ijai-5147-routing-discovery-failure

Conversation

@EugeneTheDev

Copy link
Copy Markdown
Collaborator

With a ChatGPT login, Codex looks up the workspace on chatgpt.com (accounts/check) before each model request. When that call fails (network, proxy, VPN, firewall), the turn ends with the bare text workspace routing discovery failed (or timed out). AIR reports it as a service error with only Retry.

This change:

  • explains the likely cause in the message, on v1, v2, and the AIR failure title (the original text stays in parentheses)
  • reports it as a connection failure, with the Retry and New session actions
  • reuses the existing list of "unavailable" texts from CodexThreadErrors, so the session-open and turn handling read from one list

Reproduced with real Codex 0.165.0 by pointing chatgpt_base_url at a local stub that answers 503. The output matched the report: Reconnecting… n/5, Falling back from WebSockets to HTTPS transport…, then the terminal error.

This only changes what the user sees. The connection failure itself is outside the adapter.

IJAI-5147

A ChatGPT login looks up its workspace on chatgpt.com before each model
request. When that fails, the turn ended with the bare text
"workspace routing discovery failed", reported to AIR as a service error.
Explain the likely cause and report it as a connection failure, with the
retry and new session actions.

IJAI-5147
@EugeneTheDev
EugeneTheDev merged commit b7ca688 into main Oct 28, 2026
6 of 7 checks passed
@EugeneTheDev
EugeneTheDev deleted the eugenethedev/ijai-5147-routing-discovery-failure branch October 28, 2026 21:17
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