Project: [redacted]

Project ID: 1967ddbe-fc0f-4f60-843c-cb85215de0e2

Environment: production

Service: api (23c2433a-c2de-4888-99dc-1e56260a2466)

GitHub: private repository, branch main

Every deployment triggered by a GitHub push is instantly stuck in QUEUED with: "Deployment queued due to upstream GitHub issues." Expanding the status shows Initialization, Build, Deploy, and Post-deploy all Not started. No build begins and snapshotId remains null. The current previously successful deployment is healthy and merely Sleeping via Serverless.

Already tried without success: disconnect/reconnect GitHub source; multiple fresh commits (including empty); remove old queued deployments then push again. Manual deploys through Railway Agent previously worked, but Agent Usage is now rate-limited and we will not raise it. Please do not delete/reconnect anything because production is stable.

Checks performed: status.railway.com says Fully Operational, including US West Builds and GitHub Auto-Deploys. Repository-level Webhooks is empty (Railway is installed as a GitHub App); repository Settings > GitHub Apps lists Railway App. Railway billing UI says Active Plan: Trial, $4.97 / 29 days left, no payment method. Multiple new Central Station threads with this identical queue symptom were told their hidden workspace subscription state was INACTIVE despite visible trial credit.

Please confirm the exact backend cause for this workspace/project: is an inactive subscription state blocking deployments, or is the Railway GitHub ingestion queue/backend stuck? If it is subscription-related, please explain why the UI reports "upstream GitHub issues" and shows an active Trial with credit remaining.