Your queue worker is failing to start because it cannot connect to mysql.railway.internal, which means there is no MySQL service with an active deployment in the same project. Private networking (.railway.internal) only works between services within the same project and environment. Your MySQL services exist in other projects ("acceptable-connection" and "melodious-magic"), not in "dynamic-enjoyment" where this queue worker lives. You need to either add a MySQL service to this project or use the public connection string to connect across projects.

Attempt #1 failed with service unavailable. Continuing to retry for 4m49s

Attempt #2 failed with service unavailable. Continuing to retry for 4m38s

Attempt #3 failed with service unavailable. Continuing to retry for 4m26s

Attempt #4 failed with service unavailable. Continuing to retry for 4m12s

Attempt #5 failed with service unavailable. Continuing to retry for 3m54s

Attempt #6 failed with service unavailable. Continuing to retry for 3m28s

Attempt #7 failed with service unavailable. Continuing to retry for 2m48s

Attempt #8 failed with service unavailable. Continuing to retry for 2m8s

Attempt #9 failed with service unavailable. Continuing to retry for 1m28s

Attempt #10 failed with service unavailable. Continuing to retry for 48s

Attempt #11 failed with service unavailable. Continuing to retry for 8s

1/1 replicas never became healthy!

Healthcheck failed!

As mentioned above, make sure you have an active MySQL instance running in the same environment as your service.

Hello sandyramos,

can you share your deploy logs tab output?