Approval-gated Heroku dyno lifecycle workflow. It reads current app, dyno, and formation context, then performs exactly one selected restart or stop action through recued-core.heroku. It does not create dynos, run one-off commands, scale formation, roll back releases, mutate config vars, delete resources, or call arbitrary Heroku API routes.

How it works 21 steps

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

Process (21 steps)

■ app_key trim

Trim whitespace from setting app name

■ dyno_key trim

Trim whitespace from setting dyno id or name

■ formation_key trim

Trim whitespace from setting formation type

■ app ?

■ dynos_before_raw ?

■ formation_before_raw ?

■ should_restart_dyno compare

Check if setting action equals restart_dyno

■ should_restart_all compare

Check if setting action equals restart_all

■ should_stop_dyno compare

Check if setting action equals stop_dyno

■ should_stop_formation compare

Check if setting action equals stop_formation

■ restart_dyno ?

skip: step.should_restart_dyno not_equal true

■ restart_all ?

skip: step.should_restart_all not_equal true

■ stop_dyno ?

skip: step.should_stop_dyno not_equal true

■ stop_formation ?

skip: step.should_stop_formation not_equal true

■ dynos_after_raw ?

■ dynos_before default

Apply default

■ formation_before default

Apply default

■ dynos_after default

Apply default

■ dyno_rows slice

Take a subset of

■ dyno_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

action setting = restart_dyno

heroku setting =

app name setting =

formation type setting = web

dyno id or name setting =