ENGINEERING
Detect Sentry regressions and reopen the original Linear bug
When Sentry marks a resolved issue as regressed, finds the Linear bug previously linked to that fingerprint, reopens it, and notifies the owning team's Slack channel instead…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue-regressed eventSentry
- LogicLook up closed Linear bug by fingerprintLinear
- LogicBranch: reopen existing vs. create new
- ActionReopen Linear bug + add regression commentLinear
- ActionResolve owning team from CODEOWNERSGitHub
- OutputNotify owning team's Slack channelSlack
What it does
Catches the specific case where an error you already fixed comes back. Instead of opening a fresh duplicate, it reopens the exact Linear bug that was closed for that Sentry fingerprint, flags it as a regression, and alerts the owning team in Slack.
When to use it
Use it when regressions are slipping through as brand-new tickets, losing the prior investigation history. Best for teams that close Linear bugs when Sentry issues resolve and want the full timeline preserved on a single ticket across the fix-regress cycle.
How it works
- 1Sentry emits a regression event when a previously resolved issue starts firing again.
- 2The flow extracts the fingerprint and looks up the matching closed Linear issue.
- 3A branch decides: if a prior issue exists it reopens it; if not, it creates a fresh bug.
- 4On reopen it posts a regression comment with the new occurrence count and Sentry link.
- 5It resolves the owning team from CODEOWNERS and pings that team's Slack channel with the reopened ticket.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.