Approval-gated Heroku formation scaling workflow. It reads the app, target formation, and available dyno sizes, then updates exactly one formation process type through recued-core.heroku. It does not restart or stop dynos directly, create dynos, run one-off commands, mutate config vars, roll back releases, delete resources, or call arbitrary Heroku API routes.

How it works 13 steps

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

Process (13 steps)

■ app_key trim

Trim whitespace from setting app name

■ formation_key trim

Trim whitespace from setting formation type

■ dyno_size_key trim

Trim whitespace from setting dyno size name

■ reason_text trim

Trim whitespace from setting reason

■ app ?

■ formation_before ?

■ available_sizes_raw ?

■ scaled_formation ?

■ formation_after ?

■ available_sizes default

Apply default

■ size_rows slice

Take a subset of

■ size_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

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

heroku setting =

reason setting =

app name setting =

quantity setting = 1

dyno size name setting = Standard-1X

formation type setting = web