Hi,

My Production deployment for mindnote-next has been stuck in QUEUED with the message:

“Another build is in progress. The build will start once your other Deployments have finished.”

However, I checked the deployment state across the entire team and there are no other active deployments in QUEUED, BUILDING, or INITIALIZING.

Deployment details

Project: mindnote-next Team: taehui-lee-s-projects Plan: Hobby Deployment ID: dpl_BsL8NH4n3FQz64gtQaMcxr7R3gtj Build ID: bld_ks6ik7ii6 Commit: c06fc70 Environment: Production

The internal build bld_ks6ik7ii6 already reports READY, but the Production deployment remains QUEUED.

I also have two Preview deployments for the same commit that terminated with ERROR. These Preview failures are intentional and unrelated to this issue. The project has a fail-closed configuration that intentionally prevents Vercel Preview builds from connecting to the Production Supabase project because there is currently no separate Preview Supabase project.

Therefore, the Preview errors should not be fixed or retried.

Based on the team-wide deployment state, there does not appear to be another active build occupying the Hobby plan's concurrency slot.

This looks like a stale/stuck build-concurrency or deployment queue state.

Could a Vercel team member please check the build queue/concurrency state for this team and, if appropriate, clear or reset the stale lock so the existing Production deployment can proceed?

I have not cancelled or redeployed the Production deployment yet because I want to avoid creating duplicate deployments before confirming the queue state.

Thank you.