What issue are you seeing?
Private Sites archive uploads repeatedly time out before a version is saved or deployment begins.
Latest attempt: 11 October 2026, 05:48–05:53 UTC.
Tool: sites_save_version_and_deploy_private.
Error: OpenAI file blob upload to sdmntpraustraliaeast.oaiusercontent.com failed after 300005 ms (timeout): error sending request.
Azure client request ID: 14604d43-b61d-4415-b3bf-617fb1ac3be0.
Five attempts across multiple candidates have timed out at approximately five minutes. We reduced the archive from 244.4MB to 221.5MB using pixel-exact image compression, but the timeout persisted.
The current archive contains 609 files and expands to 224.6MB. Packaging and artwork checks pass. Source-repository push/fetch and Site/version-history reads work. No new saved version or deployment appears after the failed upload.
Environment: Windows, Codex desktop app, local project, existing owner-private Site.
Please investigate the archive upload timeout using the request ID above. The exact candidate and archive are retained for further diagnostics.
What steps can reproduce the bug?
- In Codex desktop on Windows, prepare an update to an existing owner-private Site.
- Push the exact source candidate and verify it through a fresh fetch.
- Build and package the static app as a tar.gz archive containing its hosting manifest.
- Call sites_save_version_and_deploy_private with the Site project ID, pushed commit SHA and absolute archive path.
- The archive upload times out after approximately 300 seconds with “error sending request.”
- Read the Site and version history: no new saved version or deployment appears.
Reproduced across five attempts. Reducing the compressed archive from 244.4MB to 221.5MB did not resolve it. The latest archive contains 609 files and expands to 224.6MB.
What is the expected behavior?
The valid archive should upload successfully, create a saved version matching the pushed source, and deploy that version to the existing owner-private Site.
If upload cannot complete, the tool should return a specific, actionable error explaining the cause or applicable limit.
Additional information
The existing private app remains on version 82. The newer fixes are saved and pushed but cannot be delivered because the archive upload fails.
Source push/fetch and Site/version-history reads succeed. Packaging, artwork checks and local browser preview checks pass. Reducing the archive size did not resolve the timeout.
No Windows proxy or standard proxy environment variables were configured in the checks performed. The root cause remains unconfirmed.
The exact archive and its checksum are retained. Please advise what further diagnostics would help; credentials and private app data have been excluded from this report.
What issue are you seeing?
Private Sites archive uploads repeatedly time out before a version is saved or deployment begins.
Latest attempt: 11 October 2026, 05:48–05:53 UTC.
Tool: sites_save_version_and_deploy_private.
Error: OpenAI file blob upload to sdmntpraustraliaeast.oaiusercontent.com failed after 300005 ms (timeout): error sending request.
Azure client request ID: 14604d43-b61d-4415-b3bf-617fb1ac3be0.
Five attempts across multiple candidates have timed out at approximately five minutes. We reduced the archive from 244.4MB to 221.5MB using pixel-exact image compression, but the timeout persisted.
The current archive contains 609 files and expands to 224.6MB. Packaging and artwork checks pass. Source-repository push/fetch and Site/version-history reads work. No new saved version or deployment appears after the failed upload.
Environment: Windows, Codex desktop app, local project, existing owner-private Site.
Please investigate the archive upload timeout using the request ID above. The exact candidate and archive are retained for further diagnostics.
What steps can reproduce the bug?
Reproduced across five attempts. Reducing the compressed archive from 244.4MB to 221.5MB did not resolve it. The latest archive contains 609 files and expands to 224.6MB.
What is the expected behavior?
The valid archive should upload successfully, create a saved version matching the pushed source, and deploy that version to the existing owner-private Site.
If upload cannot complete, the tool should return a specific, actionable error explaining the cause or applicable limit.
Additional information
The existing private app remains on version 82. The newer fixes are saved and pushed but cannot be delivered because the archive upload fails.
Source push/fetch and Site/version-history reads succeed. Packaging, artwork checks and local browser preview checks pass. Reducing the archive size did not resolve the timeout.
No Windows proxy or standard proxy environment variables were configured in the checks performed. The root cause remains unconfirmed.
The exact archive and its checksum are retained. Please advise what further diagnostics would help; credentials and private app data have been excluded from this report.