4 hours ago
- Does Railway rollback normally redeploy the existing built image or trigger a new build?
- What do the image identifiers shown in deployment metadata and build logs represent?
- Which identifier corresponds to the deployable runtime image?
- Does the Pro-plan 120-hour retention period begin only after a deployment is removed?
- Can an active or previous deployment be pinned as a protected rollback point?
- Is there a supported method to retrieve a deployment's source snapshot, file manifest or built image?
- Is there a guaranteed-private channel through which account-specific deployment identifiers can be supplied, with no possibility of publication of the messages, attachments or responses?
1 Replies
4 hours ago
A rollback within the image retention window restores the previous deployment's image and variables without rebuilding; on Pro that window is 120 hours after a deployment is removed. A rollback outside that window falls back to a redeploy, which triggers a fresh build from the original source code. There is no feature to pin a deployment as a protected rollback point. We don't provide access to build artifacts, source snapshots, or built images for download, but if the service is still running you can pull files from the live container via the dashboard Console, railway ssh, or SCP/SFTP against ssh.railway.com. As a Pro user, you can create a Private Thread on Central Station that is visible only to you and Railway staff.
Status changed to Awaiting User Response Railway • about 4 hours ago