7 days ago
Snapshot creation step timing out after 15 minutes; service has no source configured but platform is attempting snapshot anyway.
5 Replies
7 days ago
The "dorimood-web" deployment in your development environment failed because it attempted a snapshot on a service with no source configured, which caused the initialization step to hang until the 15-minute timeout. If you need the service, connect a source (GitHub repo or Docker image) under Service Settings > Source before deploying. If this service was created unintentionally, you can safely delete it from Service Settings > Danger.
Status changed to Awaiting User Response Railway • 7 days ago
Railway
The "dorimood-web" deployment in your development environment failed because it attempted a snapshot on a service with no source configured, which caused the initialization step to hang until the 15-minute timeout. If you need the service, connect a source (GitHub repo or Docker image) under Service Settings > Source before deploying. If this service was created unintentionally, you can safely delete it from Service Settings > Danger.
7 days ago
My repo is on Gitlab so I'm using CLI from my project root to deploy on railway, same process for api and web. Until yesterday everything was working fine.
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
CLI deployments via railway up do not require a connected source repo, so the earlier suggestion to connect one does not apply to your workflow. If a fresh railway up from your project directory still fails at the snapshot step, please reply here with the new deployment ID and we can look further.
Status changed to Awaiting User Response Railway • 7 days ago
Railway
CLI deployments via `railway up` do not require a connected source repo, so the earlier suggestion to connect one does not apply to your workflow. If a fresh `railway up` from your project directory still fails at the snapshot step, please reply here with the new deployment ID and we can look further.
7 days ago
Again it is taking too long, 15+ minutes so it seems it will fail again, the ID is this: 95f39900-d749-4d5b-95f8-c764cf434689
Status changed to Awaiting Railway Response Railway • 7 days ago
s-nakov
Again it is taking too long, 15+ minutes so it seems it will fail again, the ID is this: 95f39900-d749-4d5b-95f8-c764cf434689
7 days ago
Anyone willing to take care of this?
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 7 days ago