Are you using a version tag in the image name specifier? Any : with numbers after?

No, I use latest.

I don't know if something has been done from Railway side but the latest version just deployed automaticaly.

Is there perhaps a limit on the number of deployments or updates per day, hours maybe?

no there is no limit that i have experinced even during trail mode i suggest you take a look at my post a couple weeks ago where i found a simmilar issue that i was able to fix

https://station.railway.com/questions/docker-image-seems-to-not-update-ff854bcc

Thanks. I removed some releases and push a new one but it is not picking it up for the moment (see screen capture, it has been 1 hour since the last one).
I have already enabled the auto update but not much luck. I'll wait.

To avoid overloading the respective APIs, auto updates can take up to several hours to register an update.

If you want instant deployments of new images, you will need to call our API to redeploy the service.

https://github.com/brody192/image-update-and-redeploy

Ok Thanks for the quick answer. I suspected that was the reason that why I said I'll wait. But in that case, maybe the option shouldn’t be called "At any time, immediately" then.
Thanks for the link.

Good thing you figured everything out

Thanks! Hopefuly it will help you aswell for future deployments. I'll try the API with the account token.

Thanks all for your help.

When I tried with the API, my service fails with the following error while my registry is public (GHRC on Github public repository):


I then redeploy the latest OK deployement:


and the service starts ok and updated:

Just to let you know that I tried several times and get each time the error that it cannot connect while my registry is public.

If it can help.

root@vps2:~/image-update-and-redeploy# npm start -- --serviceId=xxxxxxxxxxxxxxx --environmentId=xxxxxxxxxxxxxxx --image=poznote:latest

> image-update-and-deploy@1.0.0 start

> node dist/main.js --serviceId=xxxxxxxxx --environmentId=xxxxxxxxxxxx --image=poznote:latest

(node:1212662) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

(Use node --trace-deprecation ... to show where the warning was created)

Service updated successfully: { serviceInstanceUpdate: true }

Service redeployed successfully: { serviceInstanceDeploy: true }

Specifying the short form poznote:latest is going to cause Railway to try and pull the image from Docker, but you have the image hosted on ghcr.

Of course..... !!!! Thanks Brody !

No problem!