I am experiencing a consistent infrastructure issue when deploying my service. The assistant guided me to open this ticket with the following details so you can investigate the scheduling layer from your side:

• Service Name: evolution-api
• Deployment ID: bdc7c8da-7f8e-48de-9b87-b8a3f8b45451
• Image: atendai/evolution-api:v1.8.2 (This exact image and configuration deployed successfully back in April and was running fine).
• Current Region/Node: 1 replica on us-east4-eqdc4a

Issue Details:

The deployment consistently fails at the CREATE_CONTAINER stage. It crashes at second 00:00 before the Docker image is even pulled. There are no application logs or configuration errors being generated because the failure happens entirely within Railway's internal container-scheduling layer.

Could you please check what is blocking the container creation on that specific node or migrate the service?

Thank you!