Hey there! We've found the following might help you get unblocked faster:

• 🧵 'Cannot redeploy without a snapshot'

• 🧵 "Cannot redeploy without a snapshot"

• 🧵 Worker service failing to initialise

If you find the answer from one of these, please let us know by solving the thread!

Hi Kazunori,

The service in your Production environment is built using the Dockerfile and is listed as automatically detected. The staging environment is set to be built using Nixpacks per the Service Settings.

It appears the failed builds are those that have used Nixpacks, while the successful ones in your staging environment use the Dockerfile.

Are the up commands identical across Staging and Production?

Regards,
Christian

Thank you for your quick response! Yes, we are using the identical command. Here is a fragment of our package.json

"deploy-railway": "bun deploy-railway:setup && bun railway up --ci",
"deploy-railway:setup": "bun railway link --project=${RAILWAY_PROJECT_ID} --service=${RAILWAY_SERVICE_ID} --environment=${WB_ENV} && bun railway variables --set=\"ARCH=amd64\" --set=\"WB_VERSION=${WB_VERSION}\"",

In the staging env, can you set the `RAILWAY_DOCKERFILE_PATH` to the value where you expect the file?

Unfortunately, the same error was returned:

  Project llm-proxy linked successfully! 🎉
  Cannot redeploy without a snapshot

Can you try up ing again, this is not related to the dockerfile it seems

Hmm, still the same error occurs (but, there is no error on production environment)

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hmmm, going to chalk this up to a bug. I don't think it's worth paging the team (yet) but we will likely look into it during the rest of the day.

I see. It is not so urgent for us. During that time, we will focus on https://station.railway.com/questions/t-rpc-streams-unexpectedly-closing-on-rai-0a84e48e

Noted, we should be good now.

✅ The ticket Different build environments causing deployment issues. has been marked as completed.

Hmm, I still got: Cannot redeploy without a snapshot

Hmmm, is this solved, I see a fresh build 55 minutes ago.

I now ran railway up --ci manullay, but I still got Cannot redeploy without a snapshot

Actually, we have no new build logs: https://railway.com/project/96989012-87e4-42ae-a701-2e259144697a/service/c7674397-9293-42ac-b218-dbae98b813d5?environmentId=8185678c-d8e2-4ab0-8c5b-7a9000fdcd3c&id=f0a62f6e-d817-4757-a574-132d7f1753c6#build (though we have new deploy logs, but I confirm we have no successful deployment recently)

I see that you have a successful build. Could you let us know whether this has been resolved?

Please see the build logs: https://railway.com/project/96989012-87e4-42ae-a701-2e259144697a/service/c7674397-9293-42ac-b218-dbae98b813d5?environmentId=8185678c-d8e2-4ab0-8c5b-7a9000fdcd3c&id=f0a62f6e-d817-4757-a574-132d7f1753c6#build

The last log is written at Aug 19, 2025, 11:53 PM. After that, I cannot trigger deployment anymore due to the error: Cannot redeploy without a snapshot

For example, I now ran railway up --ci manually. As you can see, the build logs was not updated.

Even though I cannot trigger the deployment, deoloy logs were updated. I'm not sure why. However, the last deployment date is Aug 19, 2025, 11:53 PM as the screenshot shows. It means, there is no successful deployment after that time.

Could you please try to create a new environment (see the Guide in the Docs) by duplicating your production environment, set the Variables to reflect your staging environment, and test whether you can run railway up --ci manually?

✅ The ticket Issue with creating code snapshot has been marked as completed.

Hi, we are facing the same issue on another product which has already been provided to many customers, so I cannot do the strategy "remove & re-create". We need to deploy a new version within three days. Could you investigate the issue?

The project url is: https://railway.com/project/5cc5175d-4bbf-43dd-985d-c266bea6731f?environmentId=77e0d75d-529e-47ec-89f2-e6b57361f2a2

Note that we've upgraded our plan to PRO.

We have two environments: staging (https://railway.com/project/5cc5175d-4bbf-43dd-985d-c266bea6731f?environmentId=be76f315-a5d4-4998-b74c-240831db12c0) and production (https://railway.com/project/5cc5175d-4bbf-43dd-985d-c266bea6731f?environmentId=77e0d75d-529e-47ec-89f2-e6b57361f2a2).

We successfully deployed our app with the same code and same deployment script to staging (only some environment variables are different, but I'm sure that the differences are not the cause.). Moreover, we continuously successfully deployed our app to production until yesterday. So I believe production environment on your side is now something wrong.

Hello,
Can I get any of the logs on your end that you're running into? I see one on of "Failed to create code snapshot." is that the issue persisting?

We use the following command for the deployment:

yarn railway link --project=${RAILWAY_PROJECT_ID} --service=${RAILWAY_SERVICE_ID} --environment=${WB_ENV} && yarn railway variables --set=\"ARCH=x86_64\" --set=\"WB_ENV=${WB_ENV}\" --set=\"WB_VERSION=${WB_VERSION}\" && yarn railway up --ci

Here is our logs on our CI. The command always prints Cannot redeploy without a snapshot and stops.

> Select a workspace WillBooster Projects
> Select a project exercode
> Select an environment production
> Select a service app

Project exercode linked successfully! 🎉

Cannot redeploy without a snapshot

Here is the content of railway.toml :

[build]
builder = "DOCKERFILE"
dockerfilePath = "Dockerfile"

[deploy]
healthcheckPath = "/api/ping"
healthcheckTimeout = 1800
restartPolicyType = "ON_FAILURE"
restartPolicyMaxRetries = 60

We need to update our app within 12 hours, so I stopped our service and did "remove & re-create". The issue is gone. However, I'm not confrotable. Is there any other way to resolve the issue?

Hey Exkazuu!
Can you switch that services builder to "metal builder"? That has fixed the snapshot bug for some users.

Thank you for the advice. Could you explain how can I use/enable metal builder?

If you head to settings and scroll down you can enable "use metal build environment!"

Thanks, I found it. I enabled it on staging. If no issue, I'll enable it on production, too. For now, I close the thread. Thanks, again.