agent hive
Join the Waitlist

TICKET MANAGEMENT

Detect regressions in resolved Sentry crashes, reopen the ticket, and page on-call

When a previously resolved Sentry issue recurs, find its closed tracker ticket, reopen it with the new occurrence and release diff.

CategoryTicket Management
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSentry regression webhook (resolved issue recurred)SentrySentry
  • ActionLocate previously linked closed Linear issueLinearLinear
  • ActionReopen Linear issue with occurrence + release diffLinearLinear
  • LogicBranch on severity threshold
  • ActionTrigger PagerDuty incident if severePagerDutyPagerDuty
  • OutputNotify Slack + update Sentry group statusSlack

What it does

Handles the specific case of a fixed bug coming back. Rather than filing a fresh duplicate, it reopens the original ticket with proof of regression and escalates only when the recurrence is severe.

When to use it

For mature teams that mark Sentry issues resolved on deploy and need to know immediately when a fix regresses in production. Use it to keep one durable ticket per bug across its full lifecycle.

How it works

  1. 1Sentry fires a webhook on a regression (a resolved issue that recurred).
  2. 2The flow locates the closed Linear issue previously linked to that Sentry group.
  3. 3It reopens the Linear issue and posts the new occurrence, the release where it returned, and a diff against the release that resolved it.
  4. 4Branch on severity: if events-per-minute or user-impact crosses the bar, it triggers a PagerDuty incident; otherwise it just flags the issue urgent.
  5. 5It notifies the relevant Slack channel with the reopened ticket and regression context.
  6. 6It updates the Sentry group status to reflect the reopened ticket.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

More Ticket Management workflows

Deduplicate Discord bug reports against existing Linear issues

Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…

Weekly reopen-by-agent coaching digest

Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.

Promote a Discord message to a Linear issue via an emoji reaction

When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.

Enrich Discord bug reports with Sentry errors before filing in Linear

Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.

Route Discord bug reports by severity to Linear or PagerDuty

Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…

Triage Discord bug threads into structured Linear issues with repro checklists

Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.

Browse all Ticket Management →

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.

Join the WaitlistBrowse all workflows →