Approval-gated Render rollback workflow for one service and one selected deploy. It reads service, target deploy, and recent deploy context, then calls recued-core.render.deploy.rollback with the documented deployId body field. It does not update service settings, create jobs, mutate env vars/secrets, suspend/resume services, delete resources, reveal credentials, or call arbitrary Render API routes.

How it works 11 steps

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

Process (11 steps)

■ normalized_service_id trim

Trim whitespace from setting service id

■ normalized_target_deploy_id trim

Trim whitespace from setting target deploy id

■ normalized_reason trim

Trim whitespace from setting reason

■ service ?

■ target_deploy ?

■ deploys_before_raw ?

■ rollback ?

■ deploys_before default

Apply default

■ deploy_rows slice

Take a subset of

■ deploy_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.

reason setting =

render setting =

service id setting =

target deploy id setting =