Plan: Pro

Affected projects:

1. CozinhadaNutri (id: 0d53e8ba-adf6-4889-9792-4b698076478a)

- Service web (id: b8f55c88-6637-4019-b18b-a0fcf3591021)

- 8+ stuck deploys in QUEUED state (IDs: 8133e23a, 157ae308, eb8d3f93...)

2. CozinhaNutri-v2 (id: e903eb94-3dae-46b2-b719-0fe68a61ac4d)

- Created as fresh project today to test

- Same service web ALSO stuck in QUEUED

- Latest deploy: 56ff4058-2e97-47e2-91ef-a99bf19d14c9

Steps to reproduce:

- Deploy any service → BUILDING → QUEUED forever

- Applies to NEW projects and old — account-wide

- Image size is small (89 MB, Dockerfile multi-stage)

- No volumes involved on the new project

- All deployments end up in same QUEUED state

This is production system for a client — cozinhadanutri.com.br website

is effectively down because of this bug. Please manually unblock or

let me know how to proceed. I'm on Pro plan with priority support.

Reference thread:

https://station.railway.com/questions/service-deployment-stuc