[Sites] Source credential and version-list tools time out after 300 seconds

Resolved 💬 2 comments Opened Jul 30, 2026 by adoby4g-crypto Closed Jul 31, 2026

Summary

The Codex Desktop Sites connector repeatedly times out when accessing an existing Sites project. Both the source-repository credential operation and a read-only version-list operation fail after 300 seconds, which blocks a validated production release.

Environment

Codex Desktop on macOS
Date observed: 2026-07-30
Local timezone: Asia/Shanghai
Existing Sites project with a valid .openai/hosting.json project binding
Local source, build, and tests are complete; the issue occurs only in the Sites control-plane calls

Steps to reproduce

Open an existing Sites-backed local project in Codex Desktop.
Request a short-lived source repository write credential for the existing project.
Wait for the tool call.
The request fails after 300 seconds with: timed out awaiting tools/call after 300s.
Call the read-only saved-version listing operation for the same project.
That operation also fails after 300 seconds with the same timeout pattern.

Frequency

This was reproduced repeatedly across multiple attempts and separate turns. Restarting the publication attempt did not help.

Expected behavior

The credential operation returns a short-lived repo-scoped credential.
The version-list operation returns the saved versions.
Codex can then push the exact commit, save a version, deploy it, and inspect deployment status.

Actual behavior

No credential is returned.
The read-only version query also times out.
Source push, version save, and production deployment cannot begin.

Safety / impact

No token was returned or exposed.
No deployment was started, so there is no partial release.
The existing production version remains unchanged and available as the rollback point.
Project identifiers, domains, customer data, credentials, and business records are intentionally omitted from this public report; they can be supplied privately if needed.

Request for help

Please check the Sites MCP/connector control-plane availability and logs for repeated 300-second timeouts, and advise whether the project connection needs to be refreshed or whether there is a service-side recovery step.

View original on GitHub ↗

2 Comments

adoby4g-crypto · 28 days ago

Additional isolation evidence:

In the same Codex Desktop environment and account, another existing Sites project successfully returned a source repository credential in about 4 seconds and completed version save and production deployment.

Only the affected project times out. Both credential creation and the read-only version-list operation fail after 300 seconds.

This strongly suggests a project-specific App Repository or Sites control-plane binding problem rather than a local network, source-code, archive-size, or general Sites outage.

An internal feedback report with diagnostics has also been submitted. The feedback ID and affected project identifiers are available privately.

Please advise whether the affected project's source repository binding can be inspected or safely rebound while preserving its domain, D1 binding, environment variables, saved versions, and rollback history.

adoby4g-crypto · 28 days ago

Update — 31 July 2026

The Sites control-plane operations have recovered.

The source credential was returned successfully in approximately 3 seconds.
The saved-version list returned successfully in approximately 1 second.
The validated commit was saved and deployed as Version 40.
Production deployment and custom-domain verification both succeeded.
No Sites project reconnection or .openai/hosting.json change was required.

This currently appears to have been an intermittent service-side or connector availability issue rather than a local project configuration problem.

In-product diagnostic feedback was also submitted. I am keeping this issue open temporarily in case the timeout recurs during the next deployment.