Codex app: plugin search for "pstack" fails with HTTP 500 wrapping upstream 429

What version of the Codex App are you using (From “About Codex” dialog)?

26.911.7940.0, verified from the installed OpenAI.Codex Windows package.

What subscription do you have?

The Codex account usage API reports plan type prolite.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Searching for pstack on the Plugins page failed with Failed to load plugins. The remote plugin catalog endpoint returned HTTP 500, with a nested upstream HTTP 429 reporting that the per-pod concurrent query limit of 50 had been reached.

The app displayed a long backend exception, including response headers, internal runbook references, and debugging instructions.

Relevant error excerpt, with repetitive headers and internal runbook/debugging references omitted:

Failed to load plugins
search remote plugin catalog: remote plugin catalog request to https://chatgpt.com/backend-api/ps/plugins/search failed with status 500 Internal Server Error

detail.retryable: true
Upstream status: (429) Reason: Too Many Requests
x-request-id: f4653db6-802b-4db7-bb14-af5d5cab9c64
Date: Thu, 17 Sep 2026 15:42:21 GMT

Upstream response fields:
error_id: per_pod_concurrent_query_limit_reached
type: RESOURCEEXCEEDED
message: Rejecting the query because the per-pod concurrent query limit of 50 has been reached.
query_id: rs4:a33b5b40-cb39-450e-a636-a02c99ec14be:4qv9CMk:0:leaf-10d89efc-8dd3-4f27-96be-334ada33c36b

What steps can reproduce the bug?

1. Open the Codex desktop app.
2. Open Plugins.
3. Search for pstack.
4. Observe the "Failed to load plugins" error.

Feedback ID: no-active-thread-01a0b007-909d-7893-872a-ee2dcf44ec08

These are the steps taken during the reported occurrence. Repeatability and whether other search terms are affected have not been established.

What is the expected behavior?

The Plugins page should show search results. If the catalog is temporarily overloaded, the app should show a concise, actionable retry message rather than the raw backend exception and internal debugging instructions.

Additional information

Observed on September 17, 2026, at 15:42:21 UTC according to the response Date header.

The returned error points to upstream query concurrency exhaustion. The underlying service behavior and client retry behavior have not been independently investigated.

Begin with the Plugins-page search flow and reproduce the pstack query against the remote plugin catalog endpoint. Confirm how the client handles the upstream 429 wrapped in HTTP 500; done means a concise, actionable retry message is shown instead of raw backend details, with plugin results shown when the request succeeds.