We’ve run into an issue that may be unique to us, but I wanted to see if others have experienced something similar.
Our deployment queue often gets clogged with multiple commits, MRs (aka PRs), and releases since we only have one builder. Because our repo uses Turborepo, each commit triggers deployments across nine different projects, making it even harder to track what’s happening.
One challenge we faced was that Vercel simply labels deployments as “queued,” without indicating what’s ahead in the queue or causing delays. The only way to figure this out was to manually open each of our nine projects and check the deployments tab—far from ideal.
To solve this, I built a small build monitoring app using Vercel’s APIs, and it’s been working really well for us.
If this is a common pain point, I see a few potential next steps:
- Open-source the code for others to use.
- Deploy a hosted version that users can connect to via sign-in.
- See if Vercel might be interested in adopting this internally.
Would love to hear any thoughts—maybe this is just a niche issue for us, but curious if anyone else has run into it!
Our internal app to give some context:
