Approval-gated Railway deployment lifecycle workflow. It reads one deployment, performs exactly one selected restart, redeploy, rollback, stop, or cancel action through recued-core.railway, then reads the deployment again. Redeploy and rollback are skipped when Railway reports the action unavailable. It does not deploy a service instance, mutate variables, create domains or volumes, delete resources, or call arbitrary Railway GraphQL.

How it works 18 steps

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

Process (18 steps)

■ target_deployment_id trim

Trim whitespace from setting deployment id

■ deployment_before ?

■ should_restart compare

Check if setting action equals restart

■ should_redeploy compare

Check if setting action equals redeploy

■ should_rollback compare

Check if setting action equals rollback

■ should_stop compare

Check if setting action equals stop

■ should_cancel compare

Check if setting action equals cancel

■ can_redeploy compare

Check if deployment before result data deployment canRedeploy equals true

■ can_rollback compare

Check if deployment before result data deployment canRollback equals true

■ redeploy_allowed all

Check if all conditions are true

■ rollback_allowed all

Check if all conditions are true

■ restart ?

skip: step.should_restart not_equal true

■ redeploy ?

skip: step.redeploy_allowed not_equal true

■ rollback ?

skip: step.rollback_allowed not_equal true

■ stop ?

skip: step.should_stop not_equal true

■ cancel ?

skip: step.should_cancel not_equal true

■ deployment_after ?

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

action setting = restart

railway setting =

deployment id setting =

use previous image tag setting = false