Workers build queued with no other builds going on
I noticed my build is in queued status (which it never has been before), but I don't have any other builds going on. Why would it be queued? I also canceled and tried to rebuild it (it's auto triggered with code changes to github) but it still says queued. Any ideas why this would be happening?
13 Replies
looks like it went through and built now. But would still love to know why that happens or if I'm doing something weird to cause it
Actually, now my builds are failing when trying to initialize the build environment:
This is happening for multiple workers of mine all of a sudden
safe bet it's related to https://www.cloudflarestatus.com/incidents/wq7hlyz5k9bd (builds run on containers), Workers Builds should be part of that if so though, I'll mention
Interesting - yeah I'm not using containers and not based in Asia, but maybe something related?
Workers Builds run on Cloudflare's Containers platform, and they run wherever there is the capacity. Could also be the incident is wider and affecting more regions now.
ah gotcha, thanks for the info!
I just saw this thread... I was facing the same issue in https://discord.com/channels/595317990191398933/1399772186113212497. Is it wrong to say I hope this is a broader incident, and our code/data is not processed outside of the EU 😄
Workers Builds run everywhere, that part isn't a question/related to this, for example locations used last 24 hours:
I'm guessing this is affecting AMER/NA?
affecting me in europe/uk
It's not based on user geolocation, just based on wherever the system decides to try running your build
they updated the incident to include Workers Builds: https://www.cloudflarestatus.com/incidents/wq7hlyz5k9bd
seeing it in US/India
Fixed for me now. Thanks @Chaika for the info, that was really helpful!