Failed deployments
adsastralabs
HOBBYOP

a month ago

Project: ads-astra-workshop Environment: production Service: ads-astra-workshop

The problem: The build completes successfully and the image is pushed every time, but the deploy fails at the Deploy › Create container step with "Failed to create deployment." This happened across 10+ consecutive deployments.

Failed deployment IDs (sfo region):

6cc13dab-95d3-4039-a93a-a748d886bf07

7347f902-692f-4e8b-91ed-3b64b9e05075

ee6a55c9-9af5-4583-99a9-e4d8d4001051

What I've confirmed:

Code and config are unchanged from previously-successful deployments

Build succeeds and image is pushed each time (image sha256:785507a2511dc5c6a8577197de6acff79e23ad172653489fe8447c357496a69c)

The failure is isolated to container creation in sfo

Earlier deployments with the same code and configuration ran successfully

This started approximately 20:44 UTC on 2026-07-08 and persisted across 10+ consecutive deployments

Service config:

Builder: Railpack

Framework: Next.js 16.2.9

Volume mount: /data

Environment variables: RENDER_WS_ENDPOINT, DATA_DIR, ANTHROPIC_API_KEY

Networking: ads-astra-workshop-production.up.railway.app

Workaround taken: I've temporarily moved the service to iad (US East). Deployment ID: e4053688-1b7a-4b50-91e5-f7c584550736

Can you investigate container scheduling for this service in the sfo region? Is there a platform/region issue, and if so, what's the recommended resolution?

Solved

1 Replies

Railway
BOT

a month ago

Your recent deployments are failing because the service is now configured for multiple regions, which the Hobby plan does not support - Hobby is limited to a single deploy region. To fix this, remove the second region so only one remains (either us-west or us-east), and re-attach the volume (ads-astra-workshop-volume at /data), which is currently detached from the service. Once both are set, redeploy and the container creation step should succeed.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...