Project: exquisite-gentleness (formerly perfect-elegance)

Service: sales-report

Repo: jhyun860-source/sales-report (GitHub)

Tonight (KST 2026-07-15, roughly 00:00–02:00) I pushed several commits in quick

succession, and each one triggered an automatic deploy. This caused repeated

"number of concurrent builds for workspace has reached the limit" errors.

The root cause was an automated backup script that committed to GitHub every

1–3 minutes, and each commit re-triggered a new deploy — creating a redeploy

loop. I've since:

• Fully disabled the backup script in code

• Deleted the old problematic project (perfect-elegance) that was stuck

  crash-looping

• Confirmed via GitHub commit history that new automated commits have

  completely stopped since ~17:15 KST

Despite this, the newly connected service (sales-report, in the

exquisite-gentleness project) has now been stuck in "Queued" status for over

an hour with no progress (not even entering "Building").

• status.railway.com shows all green, so this doesn't appear to be a

  platform-wide incident.

• This suggests either a lingering account/workspace-level concurrent build

  limit that hasn't cleared, or a stuck/zombie build slot.

This is a business-critical app used in real time by 6 bar locations, so this

is quite urgent for us. Could you please check the concurrent build limit /

queue status for this workspace, and clear any stuck build slots if present?

Thank you.