Skip to content
Deployment image retention, reuse, and rollback conditions
youngshin0149-arch
OP

a month ago

I’m reviewing Railway’s general recovery options before a future deployment.

  1. How long are deployment images retained on each plan? Does the retention period begin when a deployment is replaced, removed, or at another point?
  2. Can a retained previous deployment image be reused without rebuilding its source? Is reuse in a separate environment supported without copying the original environment variables?
  3. What conditions must be met for rollback to a previous image? Is there a read-only way to verify image availability and rollback eligibility without triggering a deployment?

This is a general policy question. I am not requesting any deployment, restart, rollback, or configuration change.

Solved

3 Replies

Railway
BOT

a month ago

Image retention on each plan is 24 hours on Free and Trial, 72 hours on Hobby, 120 hours on Pro and 360 hours on Enterprise. The period starts when a deployment is removed, and the image is kept for that window so you can roll back to it.

Rolling back a removed deployment inside that window reuses its image without a rebuild. It creates a new deployment with that image, its settings and its variables. Once the window has passed, rollback is no longer offered. You would use Redeploy instead, which rebuilds the image from the original source with that deployment's original variables.

The condition for rollback is that the deployment is still inside your plan's retention window. Deployments outside the window don't show the rollback option at all. You can check this without deploying anything: open the service's deployment list and look at the three-dot menu on a previous deployment. A deployment you can roll back shows a Rollback option, and selecting it asks you to confirm before anything happens. More detail is in Deployment Actions and the image retention policy.


Status changed to Awaiting User Response Railway • about 1 month ago


youngshin0149-arch
OP

a month ago

Thank you for clarifying the retention policy. Two points remain:

  1. When a currently ACTIVE deployment is replaced by a successful new deployment and becomes Removed, is its original image available for rollback within the Free/Trial 24-hour retention window?
  2. Can that retained image be reused in a separate environment without rebuilding the source or copying the original environment variables and secrets? If supported, what is the documented method?

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

Yes. When a successful new deployment replaces an active one, the old deployment is marked Removed, and on Free and Trial its image stays available for rollback for 24 hours from that moment. Eligibility depends only on whether the image is still inside that window, not on how the deployment came to be removed.

A rollback only targets the same service in the same environment. We don't support deploying a previous deployment's image into a separate environment without rebuilding, so there is no method to point you to for that.

One correction to our earlier reply: a rollback restores that deployment's own service variables, but shared and Railway-provided variables come from the environment's current values, not the values at the time of the original deployment.


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...