Trigger.dev @triggerdev.bsky.social Β· May 13

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.

0 likes 1 replies

?

Replies

Trigger.dev Β· May 13

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