What this error means

A request to the Cloudflare API (/accounts/{ACCOUNT_ID}/workers/scripts/{name}/versions/{VERSION_ID}) failed. This Worker does not exist on your account. [code: 10007] is a Cloudflare failure pattern reported for developers trying to fix cloudflare workers for platforms container deployment error 10007 with dispatch namespace. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue cloudflare/workers-sdk#13936 (May 15, 2026): wrangler deploy --dispatch-namespace for Workers with containers fails because container-application registration targets /workers/scripts/ instead of /workers/dispatch/namespaces/{ns}/scripts/. Image builds and pushes succeed but registration fails with 404/10007. Category: Cloudflare (Workers SDK).

Common causes

  • GitHub issue cloudflare/workers-sdk#13936 (May 15, 2026): wrangler deploy --dispatch-namespace for Workers with containers fails because container-application registration targets /workers/scripts/ instead of /workers/dispatch/namespaces/{ns}/scripts/. Image builds and pushes succeed but registration fails with 404/10007. Category: Cloudflare (Workers SDK).

Quick fixes

  1. Confirm the exact error signature matches A request to the Cloudflare API (/accounts/{ACCOUNT_ID}/workers/scripts/{name}/versions/{VERSION_ID}) failed. This Worker does not exist on your account. [code: 10007].
  2. Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
  3. Check the build output, project root, and deployment platform configuration before redeploying.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.