1. When Sentry reports an error, the first question is what changed. This template gathers that evidence for you.
Workflow template · Engineering

Start each Sentry error with evidence

Recent commits, a careful hypothesis and a ticket, ready for responders.

SentryGitHubLinearSlack
Error created
Read recent repository commits
Investigate Sentry error
Create investigation ticket
Share investigation
  1. For each new Sentry error, OAIZ reads the ten latest commits from your GitHub repository.
  2. An LLM Call compares the error with those commits and your guide. It names a likely cause only when the evidence supports it.
  3. It files a Linear issue with the evidence and a suggested severity, then posts the summary and links in Slack.

An error, and what changed

Compared with your investigation guide

Filed in Linear, shared in Slack

Error created
Read recent repository commits
Investigate Sentry error
Create investigation ticket
Share investigation
EditorNot liveGo live
Run workflowLogsRunning workflowLogsStop watchingRun completedLogs
Starts onError created
GitHub · List Commits
Your repository, latest 10 commits
Knowledge document
Incident investigation guide
Relevant commit IDs
A suggested severity, with the reason
The check that would confirm the cause
New issue · CHK-214

TypeError in checkout total after discount change Possible cause: commit a3f9c21 changed discount rounding. Not confirmed. Suggested severity: high.

#incidents

Checkout TypeError may relate to a3f9c21. Investigation: CHK-214 in Linear, with a link to the Sentry issue.

  1. Before you go live, connect Sentry, GitHub, Linear, and Slack, then choose the repository, team, and channel.
  2. Then test it with Run workflow, and choose Go live.

Before you go live

SentryConnect Sentry
GitHubConnect GitHub
LinearConnect Linear
SlackConnect Slack
Choose the repository, team and channel
Run workflow
Not liveLiveGo live