Skip to content
How can we purge historical source snapshots without affecting a running service?
dasuya0101
OP

22 days ago

We use Railway Hobby and have removed obsolete third-party test fixtures from our current API source. Tests and capture files are now excluded from new uploads. We want to remove earlier uploaded copies while keeping the current deployment, worker services, variables and databases intact.

A read-only API check shows 14 stopped historical deployments. Twelve still have canRedeploy=true, and six remain rollback-eligible. We understand that the documented 72-hour retention for removed Hobby images may differ from retention of original uploaded source.

What retention applies to uploaded source snapshots, build caches/layers and backups? Is there a supported way to permanently delete selected obsolete source snapshots without deleting the service or project? If this requires staff help, how should a Hobby customer request a scoped purge and confirm completion?

This concerns retention of development test data, not an exposed credential, a running-service failure, or a request to stop anything. We can provide the exact project and snapshot IDs through an appropriate private channel if needed; they are omitted from this public question.

Solved

1 Reply

Railway
BOT

22 days ago

We don't offer a supported way to delete selected source snapshots, and we don't do custom deletion, cache purges or early expiry of retained copies. Source archives, images, build caches and backups all expire through their normal cleanup cycles, so there's no scoped purge to request and no completion confirmation to wait for. You don't need to delete the project, stop services, or touch your variables or databases.

The retention periods depend on the type of data. Removed deployment images are kept for 72 hours on Hobby, starting when the deployment is removed. Uploaded source archives have their own, separate lifecycle, so the image window doesn't apply to them. Build caches are cleared by regular cache cleanup, which has no fixed maximum age. Volume backups expire on schedule: daily backups after 6 days, weekly after 1 month and monthly after 3 months, and locked backups don't expire while they stay locked.

Changing your current source doesn't change existing images or source archives. Redeploying a historical deployment rebuilds from that deployment's original source, so it can bring the old fixtures back even after its image has expired.


Status changed to Awaiting User Response Railway • 22 days ago


Railway
BOT

15 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 • 15 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...