21 days ago
Every new deployment for toast-extension-hosting is failing immediately after SNAPSHOT_CODE. Railway never begins the Build stage and provides no build logs, deploy logs, failureStage, failureError, failedReason, or configErrors. The last successful deployment remains healthy and can restart normally. We have confirmed there is no relevant configuration drift between the successful and failed deployments. Can you inspect the internal orchestration logs for the failed deployment IDs and tell us why Railway is stopping before Build/container creation?
Failed deployments:
2490c69d-c1d8-41cd-b08c-63039985784a
c7fb8fdc-331e-43d1-88c6-d924b4da9c40
052e9531-7ccf-4322-99b9-7548352e4138
edd452b3-69b3-4c2b-a954-84b5942eea94
Healthy production deployment:
2b1fab41-de61-4e37-ba38-78223b1af135
The successful and failed deployments use the same node:22-alpine image, Docker/image deployment type, Railpack builder, start command, /healthz health check, sfo region, one replica, and no volume, repository, root directory, or Dockerfile.
Please do not modify, restart, or delete the healthy production deployment. We are requesting diagnosis only.
1 Replies
21 days ago
All four deployments are failing with a size-limit error because the service carries 121 environment variables, the bulk of which hold encoded binary data: TOAST_EXTENSION_PUBLIC_BUNDLE_00 through _77, plus four sets of TOAST_*_PUBLIC_CRX_* chunks reassembled by the start command at boot. Storing code and assets in environment variables is not supported, and once the total grows large enough new deployments cannot be created. To deploy again, move the binary payloads out of variables: deploy from a connected repo or image that includes the files, or fetch them at runtime from object storage (Railway Buckets, S3, or any HTTP origin). Variables are for configuration and secrets, not file content.
Status changed to Awaiting User Response Railway • 21 days ago
14 days 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 • 14 days ago