Cloudflare Developers•5mo ago

Deploy issue just started this morning

I've been deploying a lot of code and changes to my worker over the past week and this morning I started getting this error:

    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
09:55:54.681    
09:55:54.682      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
09:55:54.681    
09:55:54.682      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

The changes for this deploy weren't anything special, some logging to troubleshoot data issues. I've tried updating my wrangler and compatability date to the most recent, but still happening. I'm doing auto-deploy from Github as changes are committed and synced. Any ideas?

17 Replies

Razboy20•5mo ago

Hm, that's not good! If you try and deploy with wrangler locally through CLI, do you still encounter this issue?

Walshy•5mo ago

Hey @mattderron can you link your account so we can take a look? ?link

SuperHelpflare•5mo ago

Please use the /link command to authenticate with your Cloudflare account and link it to your Discord user. This helps Cloudflare employees access your details more quickly and provide support. It also makes future support requests easier, since your account will already be linked.

mattderronOP•5mo ago

Should be linked now, also yes I got the same error trying to deploy via CLI:

✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.

  An unknown error has occurred. If this error persists, please file a report in workers-sdk
  (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code:
  10013]

✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.

  An unknown error has occurred. If this error persists, please file a report in workers-sdk
  (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code:
  10013]

Checking in to see if you had a chance to take a look by chance? Thanks for the help!

Walshy•5mo ago

Yes sorry - should be resolved if not, let me know

mattderronOP•5mo ago

Still getting the same error when it tries to deploy:

16:22:19.896    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2/consumers/62c8b39b907d4921b05b01473f274883) failed.
16:22:19.897    
16:22:19.897      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

16:22:19.896    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2/consumers/62c8b39b907d4921b05b01473f274883) failed.
16:22:19.897    
16:22:19.897      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

Anything specific I can try or do?

Walshy•5mo ago

Hmmm Ok you're hitting a different issue to what some others were hitting, I'll ping the Queues team to look into it

mattderronOP•5mo ago

Ok thanks

Walshy•5mo ago

Queues team just reverted a change, can you retry?

mattderronOP•5mo ago

yup, one sec Got an error still, but has more info now:

16:35:51.618    This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
16:35:51.618    APIError: A request to the Cloudflare API (/accounts/***/queues/0e284cb77479483bacfb029b5ca4bd15) failed.
16:35:51.618        at throwFetchError (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
16:35:51.618        at fetchResult (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
16:35:51.618        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
16:35:51.680    This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
16:35:51.680    APIError: A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
16:35:51.681        at throwFetchError (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
16:35:51.681        at fetchResult (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
16:35:51.681        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
16:36:05.115    
16:36:05.188    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
16:36:05.188    
16:36:05.188      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

16:35:51.618    This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
16:35:51.618    APIError: A request to the Cloudflare API (/accounts/***/queues/0e284cb77479483bacfb029b5ca4bd15) failed.
16:35:51.618        at throwFetchError (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
16:35:51.618        at fetchResult (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
16:35:51.618        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
16:35:51.680    This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
16:35:51.680    APIError: A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
16:35:51.681        at throwFetchError (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
16:35:51.681        at fetchResult (/opt/buildhome/repo/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
16:35:51.681        at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
16:36:05.115    
16:36:05.188    ✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
16:36:05.188    
16:36:05.188      An unknown error has occurred. If this error persists, please file a report in workers-sdk (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code: 10013]

Walshy•5mo ago

That's Wrangler being weird :amegablobsweats: but damn, thanks - let me update the team

mattderronOP•5mo ago

I can try through wrangler cli again though, didn't do that this time same issue in wrangler cli:

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
APIError: A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
    at throwFetchError (/Volumes/DEV1/Projects/ss-workflows/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
    at fetchResult (/Volumes/DEV1/Projects/ss-workflows/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.

  An unknown error has occurred. If this error persists, please file a report in workers-sdk
  (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code:
  10013]

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
APIError: A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.
    at throwFetchError (/Volumes/DEV1/Projects/ss-workflows/node_modules/wrangler/wrangler-dist/cli.js:50466:18)
    at fetchResult (/Volumes/DEV1/Projects/ss-workflows/node_modules/wrangler/wrangler-dist/cli.js:50381:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

✘ [ERROR] A request to the Cloudflare API (/accounts/***/queues/b33dc908617d4035816092620f064ee2) failed.

  An unknown error has occurred. If this error persists, please file a report in workers-sdk
  (https://github.com/cloudflare/workers-sdk/issues) or reach out to your account team. [code:
  10013]

Sid•5mo ago

Hey, sorry about this, I'm on top of this. So far it looks like a small percentage of queues are running into this

mattderronOP•5mo ago

No worries, just let me know if you need me to do something or want me to try again. I appreciate the help!

Sid•5mo ago

Hey so I think this should work now. I was able to repro your problem with an internal-only endpoint I had, and I cannot anymore. Can you try one more time?

mattderronOP•5mo ago

yup, one sec It works! Thanks so much for your help, you all are great!

17:40:02.970    ✨ Success! Build completed.

17:40:02.970    ✨ Success! Build completed.

Just to follow-up on it - is there anything weird that I'm doing that could cause this? If so, let me know lol

Sid•5mo ago

Ah no this is not your fault at all. I'm doing some investigation today to see how we got here

Gaming

Programming

Deploy issue just started this morning

Did you find this page helpful?