CHATBOTS

Weekly Discord Digest of Top Pipeline Failure Causes

A scheduled job that aggregates the week's GitLab pipeline failures from Axiom, ranks the most common root causes.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery Axiom for last 7 days of pipeline failuresAxiom
  • LogicGroup by root cause, count MRs and authors
  • ActionWrite ranked narrative summary with LLMOpenAI
  • OutputPost weekly failure digest to DiscordDiscordDiscord

What it does

Once a week, this workflow rolls up every pipeline failure logged to Axiom, groups them by parsed root cause, and posts a ranked digest to Discord. Maintainers see which failure categories cost the most contributor-hours instead of reacting to one-off complaints.

When to use it

Use this for retro and platform-health work: it surfaces systemic CI pain (the lint rule everyone trips on, the flaky integration test, the slow runner timeout) so the team can invest in fixes with the highest leverage rather than chasing individual reports.

How it works

  1. 1A weekly schedule triggers the workflow.
  2. 2It queries Axiom for all pipeline-failure events in the last seven days.
  3. 3A logic step groups failures by root-cause category and counts affected MRs and authors.
  4. 4An LLM writes a short narrative summary highlighting the top three causes and their trend versus last week.
  5. 5The bot posts the ranked digest to the maintainers' Discord channel as a formatted embed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AxiomLog streams, queries, dashboards.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.