Cloudflare DevelopersCD
Cloudflare Developers•7mo ago•
7 replies
Tory

Containers are pretty unusable for us at

Containers are pretty unusable for us at the moment. We get a combination of failures on the majority of requests because instances are inactive (even though we removed the sleepAfter time we had defined (using latest @Cloudflare/containers 0.0.16). We get a combination of A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset. errors and this error with 5 instances sitting inactive:
There is no Container instance available at this time.
This is likely because you have reached your max concurrent instance count (set in wrangler config) or are you currently provisioning the Container.
If you are deploying your Container for the first time, check your dashboard to see provisioning status, this may take a few minutes.
Was this page helpful?