API referenceConsole
CI/CD

Babysit Render deployment

Use in console
On every Render deploy, check the build and post-deploy health and open an incident with a rollback recommendation when degraded.

Triggered when a Render deploy reaches a terminal status. For build_failed / update_failed / canceled deploys, the agent reads deploy logs and opens an incident immediately. For live deploys, it compares post-deploy error rate and latency against a 2-hour baseline using Render metrics plus any connected APM, and opens an incident when the new deploy is degraded. The incident names the service, deploy ID, commit, failing metric, and the previous succeeded commit to redeploy as a rollback. No automatic rollback — use this when you want a human to make the call.

Install

Create this automation from the CLI, or pick it in the console under Automations → New → From template.

Terminal
polylane automation from-template babysit-render-deployment

Trigger

The event that starts this automation.

Render Deploy10min delay

Fires when a Render deploy reaches a terminal status (live, deactivated, build_failed, update_failed, or canceled).

Compatible providers

1

Integrations this automation investigates and uses tools from. Connect them to unlock the full workflow.

Render

Skills

3

These skills are installed automatically when you create this automation.

/deployment-validation
/investigate-errors
/investigate-latency

Actions

1

Platform-executed side effects the agent can request. These are applied when you create this automation.

Open Incident smart

Agent instructions

The prompt the agent follows on each execution. Customize it to fit your team's playbook.

## Role You are Render Deploy Investigator. Validate the deploy that just reached terminal status; if it failed or is degraded, open an incident with evidence and a rollback recommendation. You do not roll back yourself. ## Sources 1. Trigger payload: service ID, deploy ID, status, trigger source, commit ID. 2. Render service events and deploy logs. 3. Render metrics + connected APM scoped to the service. ## Workflow 1. If status is build_failed / update_failed / canceled: pull deploy logs, summarize the failure, open an incident with severity 'high'. 2. For live deploys: compare error rate and latency against the prior 2-hour baseline. If degraded, open an incident. 3. If healthy, post a brief HEALTHY report and stop. ## Output Incident body should include: service ID, deploy ID, commit, evidence (logs or metric comparisons), recommended rollback (redeploy previous succeeded commit). ## Operating rules - Cite metrics with provider, query, and time range. - Do not open an incident for healthy deploys. - Use severity 'critical' for full-outage signals, 'high' for build failure or elevated error rate, 'medium' for latency-only degradation.

Parallel passes

Each execution runs multiple analysis passes with different perspectives, then aggregates the results.2 passes

How it works

When a render deploy event occurs, an agent runs the instructions above, investigating with your connected Render tools, and sends results to your configured destinations.

Destinations

When you create this automation your email is added as a destination, so every run lands in your inbox. Add chat or webhook destinations afterward.

Related templates

Daily Render infrastructure audit
Run a daily audit of your Render observability setup and flag gaps in monitoring
Cloud compliance audit
Weekly audit of IAM policies, resource tagging, and governance compliance across cloud providers
Track deployments from CI/CD pipelines
Receive deployment notifications from any CI/CD system and correlate with infrastructure health
Back to templates