You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cloudflare Workers assets-upload-session fails with HTTP 500, error 10013 #149
Operating system: Windows 11 (Acer laptop)
Node.js: Version not confirmed
Wrangler: 4.151.0 installed
Deployment method: Custom guarded Node.js script using the Cloudflare REST API
Worker: fire-stripe-test-20261101
Application: FIRE Business App, PR cloudflare/workers-sdk#228
Please provide a link to a minimal reproduction
No public minimal reproduction is available yet. The failure occurs during an authenticated Cloudflare Workers asset-upload-session request. A similar issue was reported here: cloudflare/workers-sdk#16571 I can provide additional sanitized diagnostics if needed.
Describe the Bug
On November 12, 2026, an authenticated Cloudflare Workers asset-upload-session request failed with HTTP 500 and error code 10013.
The request failed before asset uploads or inactive Worker version creation.
An authenticated read-only check afterward confirmed the original Worker remained at 100% traffic, with its original TEST database, Cloudflare Access enabled, and Stripe disabled.
Only one upload attempt was made. No automatic retries were performed.
Please investigate why the asset registration API returned HTTP 500 / code 10013 and whether this is a provider-side problem, permission issue, or manifest validation failure.
Please provide any relevant error logs
Date: November 12, 2026
Cloudflare API response: HTTP 500
Cloudflare error code: 10013
Failed operation: POST assets-upload-session
Terminal output:
STOP: Gate9 inactive upload [POST_REGISTRATION_HTTP_500_CODE_10013]; reconcile before retry.
A related report, #16774, describes an assets-upload-session failure with error 10013 and Wrangler 4.151.0. That version is also installed in our environment, although our failed operation used a guarded direct Cloudflare REST API request.
Our November 12 attempt returned HTTP 500 / code 10013 during the initial asset-registration POST, before asset upload or Worker version creation.
We made only one attempt. A subsequent authenticated read-only check confirmed the original TEST Worker remained active at 100% traffic, with no deployment change.
Could the Workers Assets team investigate whether this relates to the same underlying platform problem and advise on provider-side diagnostics before another attempt?
We can provide additional sanitized information if needed.
Activity
kylebrooks86 commentedon Nov 13, 2026
Additional evidence for this issue:
A related report, #16774, describes an assets-upload-session failure with error 10013 and Wrangler 4.151.0. That version is also installed in our environment, although our failed operation used a guarded direct Cloudflare REST API request.
Our November 12 attempt returned HTTP 500 / code 10013 during the initial asset-registration POST, before asset upload or Worker version creation.
We made only one attempt. A subsequent authenticated read-only check confirmed the original TEST Worker remained active at 100% traffic, with no deployment change.
Could the Workers Assets team investigate whether this relates to the same underlying platform problem and advise on provider-side diagnostics before another attempt?
We can provide additional sanitized information if needed.