Skip to content

Cloudflare Workers deployment fails with API error 10013 #155

Open

Description

@eniyihalin-dev

What versions & operating system are you using?

I have a Cloudflare Worker connected to a private GitHub repository.

The existing Worker is running successfully, but new deployments fail with the following error:

A request to the Cloudflare API (/workers/scripts/emlak-agent-panel/versions) failed. An unknown error has occurred. [code: 10013]

The repository is cloned successfully, Wrangler runs, and the KV namespace binding is detected.

The same unknown error also occurs when attempting to deploy directly from the Cloudflare dashboard code editor.

  • Worker: emlak-agent-panel
  • Wrangler: 4.161.0
  • Deploy command: npx wrangler deploy
  • Git branch: main

Could you help identify why new Worker versions cannot be created?

Please provide a link to a minimal reproduction

https://github.com/eniyihalin-dev/emlak-agent

Describe the Bug

The repository is private. I can provide a minimal public reproduction if required. The same deployment error also occurs through the Cloudflare Dashboard editor.

Please provide any relevant error logs

No response

Activity

  1. workers-devprod commented on Nov 13, 2026

    @workers-devprod
    Collaborator

    Automated triage

    Issue assessment

    • Actionability: ⚠️ Needs information.
    • Type: Bug.
    • Reproduction: Automatic attempt requested.
    • Labels:
      • bug (high)
      • package:wrangler (high)
      • api (medium)
      • not-in-wrangler (medium)
    Actionability and missing information

    Deployment of a Git-connected Worker fails with Cloudflare API error 10013 on the script versions endpoint via both wrangler deploy and the dashboard editor; the linked reproduction repository is private and no OS or detailed logs are given.

    Reproduction reason: The report describes a current Wrangler deploy failure with a concrete API error, so an attempt is warranted, though the linked repository is private and may be inaccessible.

    Missing information:

    • minimal reproduction
    • environment
    • error output

    This summary was generated by an LLM and may contain errors. Please verify its findings.

    Triage bot commands and options

    Repository collaborators with write or admin access can trigger actions by commenting on this issue:

    • @workers-devprod reproduce: Attempt to reproduce the issue using its description and recent comments.
  2. moved this from Untriaged to Backlog in workers-sdkon Nov 16, 2026
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

    bugSomething isn't working

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions