worker deployment using wrangler fails [code: 10013]
While deploying worker (using wrangler) I'm getting next error:
Additional information:
Issue started today. Deploying old artifacts (which were successfully deployed yesterday) - results in same error.
worker routes were not changed
7 Replies
Hey @wzzzup. , is this for your staging account? I see some failures for timeouts, but looks to be an internal issue on our end if this is the case (account tag ending in
ecc)@Will Taylor | Workers yes (account tag ending in ecc) is our stg acc, currently observing the issue on stg acc (don't know about prod - as stage failure is blocking me from deployment to prod).
fyi: we have several workers on that (stg) acc. all were deployed successfully except one where I'm seeing this error
Ah, I think I see the issue. We're trying to get a fix out for this, but dependent on some other teams... I think the problem is with some inefficiencies in the zone lookup. By chance, are you specifying several routes, but only with a pattern?
for that particular worker I have ~ 80 routes mapped. They all look like this "www.something.stgsubdomain.com/*"
It might be a bit of a pain, but if you can add a zone_name or zone_id, I think that would do the trick. (https://developers.cloudflare.com/workers/configuration/routing/routes/#set-up-a-route-in-the-wrangler-configuration-file)
added "zone_id" to routes mapping - deployment passed
cool, sorry about that! you're not the first to hit this 🙁