Builds Infinitely Queued With No Other Builds Running
Hey! I'm trying to build my worker right now but am running into an issue where my builds are running stuck at "Queued" because there are other builds running, however there are no other builds on my account so I'm kind of curious what's happening here and how I would fix it?
24 Replies
Well, good news or bad, I joined this server a few minutes ago to discuss exactly the same issue.
So, yay that maybe it's not me?
And "oh crap" that there might be something wrong with builds?
In my case, I can cancel the later infinitely-queued build, but the earlier one that started this mess just won't cancel (even though it shows a status of "canceled" in the list.) Inside the build that just keeps going, the infinitely-repeated message is
Build initialization failed: unable to verify Worker.
Hey, sorry for the issue. There was an incident our side which caused this:
https://www.cloudflarestatus.com/incidents/bhsk2l01d5pm
It should now be resolved.
perfect, thanks!
@Walshy I'm still having trouble with this. Any new build (either as a Retry Build of one that should have worked or a triggered build from git) goes into Queued status forever.
The earlier stuck build in my build history—the one right after commit 289403b in the picture above—still says "Cancel Build" instead of "Retry Build" in the actions menu, no matter how many times I hit "Cancel Build".
(Also, just as an aside, of course this would happen when I'm trying to deply a bug fix of my own 🤣 ! So ... the longer I'm stuck, the longer I can't fix bugs that I actually caused.)
what's your account id?
edd49a7e4fc7d14ce0985f1a3eee6bb6
Thanks, I've passed to the builds team
Hi @SparkInChief we're working on fixing this
Thanks so much, @Maximo ! Workers is a great product and I appreciate your work on it—being able to trigger builds is amazing.
To test while you're looking at things, I confirmed that new builds also get infinitely queued for other workers in my account that didn't have a bad build during the incident.
Hey @SparkInChief , could you check in to see if your builds are fixed now?
Very nicely done. Both show completed.
Awesome, thank you :) Sorry for the headache!
No worries, when you're that fast about fixing things you get a MAJOR pass on headaches.
hi, is this still an issue? i seem to be having the same problem today and wondering if it's on my end, maybe i have a configuration issue?
Hey @Skam, can you provide your account id?
hi @Maximo sorry I was in work, just saw your message. i'll find that id now
found it
5ab32037881b672950a7fcd98148ddc9
Hmm, don't see any builds under that account, could you share the
build id instead?
When you're viewing your build logs, it should appear in your address bar like this /production/builds/<build_id>of course, it's
7d6c5aab-b964-4111-a01f-3f66419f270b
i just retried the build about 5 mins ago, the one from last night timed out. this one is still running
Ahh I see, it seems like your builds are timing out after the npm install step. Is that what you also see in your build logs?
it is!
it runs for around 20 minutes then fails and times out
We're working on some improvements here, for now could you try using a different package manager like
pnpm and see if that improves things for you?
I'm curious to see if it makes a difference, does this project have a lot of dependencies?i'll give it a try and will come back with an update! may take a while as i'm not very experienced with node/npm/etc
it does have a decent amount of dependencies, around 61 from what i can tell
the project itself is called quartz (https://github.com/jackyzha0/quartz)
thank you for sharing! yes, do let me know if
pnpm helps!