- 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.




Error created
Read recent repository commits
Investigate Sentry error
Create investigation ticket
Share investigation
- For each new Sentry error, OAIZ reads the ten latest commits from your GitHub repository.
- An LLM Call compares the error with those commits and your guide. It names a likely cause only when the evidence supports it.
- 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
Starts on
Error created
Error createdGitHub · 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-214TypeError in checkout total after discount change Possible cause: commit a3f9c21 changed discount rounding. Not confirmed. Suggested severity: high.
#incidentsCheckout TypeError may relate to a3f9c21. Investigation: CHK-214 in Linear, with a link to the Sentry issue.
- Before you go live, connect Sentry, GitHub, Linear, and Slack, then choose the repository, team, and channel.
- Then test it with Run workflow, and choose Go live.
Before you go live
Connect Sentry
Connect GitHub
Connect Linear
Connect SlackChoose the repository, team and channel
Run workflow
Not liveLiveGo live