Your workspace has a concurrent build limit, and with 18 services all connected to the same GitHub repo without watch paths, every single commit triggers 18 simultaneous builds, which hits that limit. Until you configure watch paths, every commit will continue to run into this. Configure watch paths on each service so that a push only triggers builds for services where relevant files changed. For example, if a service only needs files under /packages/backend, set its watch path to /packages/backend/**. Once watch paths are in place, a single commit will only build the affected services instead of all 18, keeping you well within the limit.

Thanks for the quick response, mykal. Watch paths have already been configured for all 18 services overnight (16 factory services → factory/**, and the analysis-ui service → specific file patterns). That part is done.

However, builds are still failing. The root issue appears to be an elevated riskLevel (0.5) on our workspace, triggered by the ~50 rapid redeploy attempts last night. Even with 0 active builds, every new redeploy attempt immediately fails with the concurrent build limit error.

Could you please help reset the riskLevel / clear the build counter on our workspace? A critical payment integration fix (PR #62) is waiting to deploy to twcb-analysis.up.railway.app and is currently completely blocked.

Same issue here (PRO plan) — same root cause. Our two services (backend + frontend) had watchPatterns = ["**"], which caused every commit to trigger builds for both services simultaneously. ~25 rapid redeploy attempts today exhausted the workspace build limit and appear to have elevated our riskLevel.

watchPatterns fix: already merged today (PR #853) — both services now scoped to ["backend/**"] and ["frontend/**"] respectively.

However, all subsequent builds still fail at "scheduling build on Metal builder production-builderv3-us-east4-3cm3" and never proceed. The service is running from an older deployment (~3 hours ago) and we have 20+ commits waiting to deploy.

Project ID: c7d3a3a1-c60f-418c-9798-757ce9ff3d3d

Service (backend): e08841a0-aadc-4462-b6af-1ecb3e9f6c80

Example failed deployment: 2da754bb-ae8f-491c-b6b0-9975d509bba6

Could you please reset the riskLevel / workspace build counter for our workspace? Critical features are blocked. Thank you.

Hello again,

I did some more digging and can confirm that there are some stalled deploys at play here that are filling up your concurrent deploy limits. Your risk level is not at all related to how your build queue is handled- I am digging in now and will update when you should be cleared to deploy again.

I apologize for the inaccurate diagnosis earlier but I am glad to hear you've got watch paths setup- that should help ensure only the services that need deploys get them.

I'll reach out as soon as I have things sorted.

Hey! this should be sorted for your account. I left a comment on your thread.

Please let me know if you're still seeing problems over there 🙂

Looks to be resolved!

You'll just need to redeploy / retrigger deploys on the affected services and everything will come back up.

Going to mark this as solved but feel free to reply to re-open if you're still having issues.