23 days ago
Hi ,
I'm need clarification about deployment image retention and rollback safety.
- Is there a supported read-only method to verify the immutable OCI image digest, manifest and configuration associated with an existing Railway deployment?
- Can I independently verify whether an earlier deployment image is still retained and recoverable?
- If an earlier deployment is no longer rollback-eligible, does redeploy rebuild from source rather than restore the original immutable image?
- Can these checks be performed without restarting, redeploying or modifying existing services?
I'm requesting platform-level guidance only, not application debugging or changes to my environment.
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
We don't provide a way to download or export a deployment's built image, manifest or image configuration, so independently inspecting those artifacts isn't something we offer.
The supported way to check whether an earlier deployment is still restorable is the deployment menu on that deployment: if Rollback is offered, its image is still within your plan's retention window, and rollback restores both that image and its variables. On Hobby, images of removed deployments are retained for 72 hours from removal, and deployments older than the retention policy don't show the Rollback option. Opening that menu is read-only and doesn't restart or change anything; only confirming an action does.
Once a deployment is past that window, Redeploy builds again from that deployment's original source and build/deploy configuration rather than restoring the original image, so the result is a new build, not the earlier image.
Status changed to Awaiting User Response Railway • 23 days ago
16 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 • 16 days ago