Skip to main content
Turn your Sentry backlog into a self-clearing queue. This scheduled automation wakes Devin up every morning, pulls the top N unresolved Sentry errors from your projects, investigates each exception in the codebase, and opens ready-to-review fix PRs — so your team starts the day with solutions instead of stack traces.

Use this template

Open Daily Sentry Error Fixes in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Daily Sentry Error Fixes.

​
What this automation does

Instead of a human triaging Sentry every morning, Devin does it for you on a cron schedule. The built-in Sentry MCP gives Devin read access to your Sentry organization, so it can rank issues by user impact, pull full event payloads, reproduce the failure locally, and push branches with targeted fixes.

​
How it works

Trigger: Schedule event — recurring
  • Event: schedule:recurring
    • Conditions:
      • rrule matches FREQ=DAILY;BYHOUR=6;BYMINUTE=0
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

  • MCP servers:

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Daily Sentry Error Fixes. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Chewing through production error backlog without tying up engineering time
  • Cleaning up low-priority “we’ll get to it” Sentry issues that never actually get fixed
  • Turning each morning’s standup into a PR-review meeting instead of a triage meeting
  • Keeping unresolved counts flat even while shipping at high velocity

​
Customization ideas

  • Change the cadence (hourly, daily, weekly) with a custom cron expression
  • Narrow the query to a single Sentry project or environment
  • Raise or lower the “top N” cap to balance cost vs. coverage
  • Attach a playbook with your team’s error-fix conventions (testing, logging, monitoring)

​
See also