Your CarWashBusiness service in the System-iT project shows the latest deployment has moved from QUEUED to FAILED status. The evolution-api service in the same project also shows FAILED. Since the deployment is no longer stuck in QUEUED, you can trigger a new deploy by clicking the three dots on the failed deployment and selecting "Redeploy," or push a new commit to trigger a fresh build.

there is a messagem in my page: Limited Access

Deploys have been paused temporarily. Please review my subscription, I'm receiving message to upgrade to hobby, but I'm a hobby subscription

Hey, sorry for the disruption. During high-load periods or platform incidents we sometimes pause Hobby/Trial deploys temporarily to keep the platform stable while the queue drains; more on that here: https://docs.railway.com/deployments/reference#deployments-paused---limited-access.

The most recent incident is resolved, the queue has drained, and Hobby/Trial deploys are processing normally again. Trigger a redeploy from the dashboard or CLI and it should go through.

Thanks for hanging in there and let us know if anything still looks off.