Skip to content

Cloudflare Workers assets-upload-session fails with HTTP 500, error 10013 #149

Open

Description

@kylebrooks86

What versions & operating system are you using?

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.

Application: FIRE Business App
Worker: fire-stripe-test-20261101
GitHub PR: kylebrooks86/first-in-response-website#228

The application passed all offline verification, including 188 Worker modules, 41 client assets, and an independently verified SHA-256 digest.

The upload used a guarded Node.js script calling the Cloudflare REST API.

The failure occurred at:
POST /accounts/{account_id}/workers/scripts/{script_name}/assets-upload-session

Error:
STOP: Gate9 inactive upload [POST_REGISTRATION_HTTP_500_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.

Local preflight: PASS
Worker modules verified: 188
Client assets verified: 41
Post-failure read-only verification: PASS
Existing Worker remains at 100% traffic.

No automatic retries, active deployment, or database changes.

Activity

  1. added theissue type on Nov 12, 2026
  2. kylebrooks86 commented on Nov 13, 2026

    @kylebrooks86
    Author

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions