Errors: find and fix your bugs faster.
You can now quickly track down whatβs causing your runs to fail with error alerts. Then bulk replay when youβve shipped the fix.
β
2
3
21
1,682
Failed runs get fingerprinted by error type and message, with dynamic parts (IDs, timestamps) stripped.
200 instances of `ππππ πππ-π·πΈπΉ πππ πππππ` and `ππππ π‘π’π£-π½πΎπΏ πππ πππππ` collapse into one row with a count and a timeline.
1
139
Alerts fire once per error group, not once per failed run.
(Slack timestamps use `<!ππππ^>` tokens, so London + SF in the same channel render their own time.)
May 13, 2026 Β· 4:55 PM UTC
1
112
Every error has a status: unresolved, resolved, or ignored.
Mark resolved when you've shipped the fix. Ignore for hours or days when you're not ready to deal with it. Bulk actions on the list let you triage many at once.
1
39
Replay every run in an error group with one click.
For when a bad deploy nuked 200 jobs and you've just shipped the fix.
1
42
The list and individual error page filter by task version. The chart stacks errors by version.
The shape of a fix landing: a tall bar that tapers off the moment `ππ·.πΊ.π½` ships.
1
294
Live in the dashboard now.
Open Errors in the sidebar of any project: trigger.dev/changelog/errors
1
240