[Windows desktop] Workspace routing is unavailable: status 432 in Chat-related requests

Sanitized application logs

Time window: 2026-09-20 13:37:00–13:43:59 UTC (21:37:00–21:43:59 UTC+08:00).

Source: %LOCALAPPDATA%\Codex\Logs\2026\09\20\codex-desktop-[session-redacted]-[pid-redacted]-t0-i1-132812-0.log

94 sa_server_request_failed events in this window record errorMessage="Workspace routing is unavailable" and status=432.

Selected entries, reduced to diagnostic fields (timestamps and line numbers preserved; identifiers and request headers omitted; query parameters omitted):

L889  2026-09-20T13:38:39.512Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=get status=432 url=/accounts/verified_access
L1017 2026-09-20T13:39:32.008Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=get status=432 url=/settings/user
L1021 2026-09-20T13:40:36.934Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=get status=432 url=/celsius/ws/user
L1022 2026-09-20T13:40:36.935Z warning [electron-message-handler] chatgpt_pubsub_connection_failed errorMessage="Workspace routing is unavailable" retryCount=5
L1023 2026-09-20T13:40:36.935Z warning [electron-message-handler] chatgpt_pubsub_reconnect_exhausted retryCount=5
L1216 2026-09-20T13:42:57.573Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=post status=432 url=/conversation/init
L1220 2026-09-20T13:42:57.574Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=get status=432 url=/models
L1285 2026-09-20T13:43:26.531Z warning [electron-message-handler] sa_server_request_failed errorMessage="Workspace routing is unavailable" method=get status=432 url=/conversations

Limits of the log evidence

• Request IDs: not found in the 94 request-failure events.
• Raw HTTP responses and response headers: not found. 432 is the application's logged status; these excerpts do not establish whether it originated on the server or in the desktop request layer.
• The connection-failed and reconnect-exhausted events do not themselves record an HTTP status, request path, or request ID.
• Policy-acknowledgment request, workspace policy, acknowledg, and the full policy-acknowledgment dialog text: not found in this window. This absence does not establish request success.
• Four generic policy matches concern Codex permission/sandbox configuration and were excluded as unrelated.
• The excerpts are structured application error events, not user prompts.

Start with the sanitized log at %LOCALAPPDATA%\Codex\Logs\2026\09\20\codex-desktop-[session-redacted]-[pid-redacted]-t0-i1-132812-0.log and trace the electron-message-handler failures for status 432. Check the listed request paths and pubsub reconnect events first. Done means the workspace-routing failure is identified and the affected Chat-related requests and connection recover as expected.