Issue Summary

My Resume-Master service has three consecutive deployments stuck in QUEUED status with no progression to build or deploy stages. Manual redeploy attempts do not resolve the issue.

Affected Deployments

37c67bb5-5cd2-4bd1-9eee-c16f52a2ecb8 — queued since 2026-07-22 18:19:56 UTC

a6b3fb8d-a7e1-411a-93dc-64f49e9243e3 — queued after first manual redeploy attempt

0b7d760a-3dc2-4d2b-aec2-a679384b3647 — queued after second manual redeploy attempt

Timeline

2026-07-20 14:32 UTC: Last successful deployment (1076a452-5c31-40c0-ac1d-5efab3d0820a)

2026-07-22 18:19 UTC: First new deployment triggered (queued)

2026-07-22 18:XX UTC: Attempted manual redeploy → queued again

2026-07-22 18:47 UTC: Second manual redeploy attempt → queued again

Service Configuration

Service Name: Resume-Master

Service ID: c07adf2a-906b-44ef-bed1-a9c4e703f5b4

Project: lovely-vitality (ID: 26e96c48-edea-4b68-a6c9-d044fde73afb)

Environment: production (ID: 84582052-97db-4489-95cb-e26f980fee59)

Plan Tier: Hobby

Region: us-west (sfo) with 1 replica configured

Repository: Ignotus-21/Resume-Master, branch: main, root directory: /backend

Builder: Railpack (auto-detected)

Start Command: (default)

Health Check: (none configured)

Commit Details (Latest Deployment)

Commit SHA: 223460c929777d8010a175985ced82f6fbe11b99

Commit Message: "Add support contact API and welcome email on verification (#51)"

Commit Status: ✅ Merged on GitHub with no errors

PR: #51 (resolved, no blocking checks)

Diagnostics Performed

✅ Service configuration is valid (1 of 5 services on Hobby plan)

✅ GitHub commit is clean and merged

✅ No build or deploy errors reported by Railway platform

✅ No service config errors detected

✅ No workspace resource quota violations

✅ Manual redeploy attempts trigger new deployment IDs (not stuck retrying the same deployment)

✅ Previous deployment (2026-07-20) completed successfully

Issue: All three new deployments remain in QUEUED status indefinitely with no progression. The platform is not starting the build phase for any of them.

Suspected Root Cause

Platform-side builder queue bottleneck or infrastructure issue. The service config and commit are valid; the blockage appears to be in Railway's build infrastructure.

Questions for Support

Is there a known builder queue issue or infrastructure degradation on 2026-07-22?

Can you manually restart the builder queue or cancel stuck deployments?

Should I take any action on my end to unblock this?