Approval-gated Vercel rollback workflow. It reads the project, target rollback deployment, and recent rollback candidates, then requests a rollback through recued-core.vercel.deployment.rollback. It never creates deployments, promotes unrelated deployments, pauses projects, mutates domains or environment variables, deletes records, or calls arbitrary Vercel APIs.

How it works 16 steps

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

Process (16 steps)

■ project_id_trim trim

Trim whitespace from setting project id

■ deployment_id_trim trim

Trim whitespace from setting deployment id

■ team_id_trim trim

Trim whitespace from setting team id

■ team_slug_trim trim

Trim whitespace from setting team slug

■ description_trim trim

Trim whitespace from setting description

■ has_project compare

Check if project id trim has data

■ has_deployment compare

Check if deployment id trim has data

■ ready all

Check if all conditions are true

■ project ?

■ rollback_deployment ?

■ candidates_raw ?

■ rollback ?

skip: step.ready not_equal true

■ candidates default

Apply default

■ candidate_count count

Count items in candidates

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

vercel setting =

team id setting =

team slug setting =

project id setting =

description setting =

deployment id setting =