Sites artifact upload consistently times out after 60 seconds

Summary

A verified ChatGPT Sites deployment artifact repeatedly fails during the pre-version blob-upload stage. The failure occurs at the same 60-second boundary before any Sites version is created. This is a Sites artifact-upload problem, not website-code troubleshooting.

Uploaded diagnostic thread: 019c0d37-d2b6-74c0-918f-0e64af9b6e14

Environment

• ChatGPT/Codex desktop: 26.903.71938 (build 8576)
• Bundled Codex CLI: 0.153.4
• macOS: 26.6.2 (build 25G83)
• Artifact size: 80,832,874 bytes (77.09 MiB)
• Archive entries: 3,056
• Approximate expanded content size: 152,403,315 bytes
• Artifact SHA-256: be1ae354ac21b671d76191012b2c59e4dbbfbe7fe14cd9e1a90db52b97e08609

Observed behavior

The identical artifact failed three times at the upload boundary. No saved Sites version was created.

Latest attempt:

• Started: 2026-09-16T00:13:44Z
• Failed: 2026-09-16T00:14:45.198Z
• Azure client request ID: 556d65f5-9144-4b1d-b79d-2d6e483c234f

Exact error:

tool call error: failed to upload /private/tmp/fmm-premium-site-polish-2d0d0c3-rebuilt.tar for archive: OpenAI file blob upload to sdmntpreastus2.oaiusercontent.com failed after 60000 ms (timeout, azure_client_request_id=556d65f5-9144-4b1d-b79d-2d6e483c234f): error sending request

The available Sites upload operation exposes no configurable timeout, resumable-upload option, or mechanism for referencing a partial upload. Source-only remote building is not equivalent because this deployment must use the exact verified artifact.

A read-only check found no enabled macOS HTTP, HTTPS, SOCKS, PAC, or proxy auto-discovery settings. No additional upload was attempted after escalation.

Expected behavior

The exact verified artifact should upload successfully, or Sites should provide a supported longer deadline/resumable upload mechanism for artifacts of this size.

Request

Please investigate the blob-upload request using the Azure request ID and advise whether the fixed 60-second deadline can be extended or replaced with a resumable upload path.

Production remains unchanged on the prior healthy Sites version.

Start by tracing the Sites artifact-upload path in the Rust repository and correlate its Azure blob request with diagnostic thread 019c0d37-d2b6-74c0-918f-0e64af9b6e14 and request ID 556d65f5-9144-4b1d-b79d-2d6e483c234f. Determine whether the fixed 60-second deadline or resumable upload behavior can be changed, then verify that the exact artifact uploads successfully without creating an incomplete version.