SUMMARIZATION

Slack Crash-Free Regression Digest on a Schedule

Runs daily, compares crash-free rates across your three most recent Sentry releases.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionPull crash-free rates for the three latest Sentry releasesSentrySentry
  • LogicDetect regression vs prior two; end quietly if within tolerance
  • ActionWrite a short regression narrativeOpenAI
  • OutputPost the verdict to the Slack release channelSlack

What it does

Once a day this workflow reads crash-free session rates for the last three Sentry releases, decides whether the newest deploy is a regression, and — only if it is — posts a concise written explanation to a Slack channel. Healthy days stay quiet, so the channel signal stays meaningful.

When to use it

Use it when you want a low-noise stability watch on your release train. It suits on-call rotations and release captains who would rather get one clear sentence about a real regression than a dashboard they have to remember to check.

How it works

  1. 1A daily schedule triggers the run.
  2. 2The flow pulls crash-free session and user metrics for the three latest Sentry releases.
  3. 3A logic step computes the delta against the prior two and checks it against your tolerance; if within tolerance, the run ends silently.
  4. 4When a regression is detected, an LLM step writes a short narrative explaining which release dropped, by how much, and the trend shape.
  5. 5The verdict is posted to your designated Slack channel with the release version and numbers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.