Skip to content
Recued
Menu
← Back to recipes

Restore Railway volume backup

by recued-core v1

Approval-gated Railway volume restore workflow. It reads one volume instance and its backups, then restores exactly one selected backup through recued-core.railway. It does not create backups, delete backups, delete volumes, mutate services, deploy code, mutate variables, or call arbitrary Railway GraphQL.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)
target_volume_instance_id trim
Trim whitespace from setting volume instance id
target_volume_backup_id trim
Trim whitespace from setting volume backup id
volume ?
backups_raw ?
restore ?
backups default
Apply default
backup_rows slice
Take a subset of
backup_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

railway setting =
row limit setting = 12
volume backup id setting =
volume instance id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Railway connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.volumeinstancebackuplistdata.volumeinstancedata.volumeinstancebackuprestore

About

Tags

railway railwayvolumebackuprestoreapprovalpack:railway

Details

9 steps 4 configurable settings recipe_id: restore-railway-volume-backup