Use “Render deploy investigation brief” in Recued. It provides a read-only AI-assisted investigation brief for one Render deploy.

How it works 22 steps

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

Process (22 steps)

■ normalized_service_id trim

Trim whitespace from setting service id

■ normalized_deploy_id trim

Trim whitespace from setting deploy id

■ service ?

■ deploy ?

■ deploys_raw ?

■ events_raw ?

■ jobs_raw ?

■ defaults defaults

Apply defaults

■ event_count count

Count items in events

■ job_count count

Count items in jobs

■ deploy_rows slice

Take a subset of

■ event_rows slice

Take a subset of

■ job_rows slice

Take a subset of

■ deploy_context map

Extract from each item

■ event_context map

Extract from each item

■ job_context map

Extract from each item

■ ai_context merge

Combine objects together

■ summarize ?

■ deploy_table to_table

Format results as a data table

■ event_table to_table

Format results as a data table

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

focus setting = Summarize this Render deploy for a developer and on-call owner: current status, commit context, nearby deploys, service-event types, job states, likely risks, and concrete next triage steps. Use only the allowlisted fields provided and do not invent facts.

render setting =

deploy id setting =

row limit setting = 20

max length setting = 900

service id setting =