DATA OPS
Snowflake Freshness Breach RCA Agent: Investigate and Draft Incident Report
On a freshness breach, an agent investigates likely causes across the warehouse, orchestration logs, and recent code changes.
How it runs
The automated pipeline, trigger to output.
- TriggerFreshness breach webhookHTTP webhook
- ActionPull load history + errors from SnowflakeSnowflake
- ActionFind recent commits on the modelGitHub
- LogicForm leading hypothesis + confidence
- ActionDraft RCA page in ConfluenceConfluence
- OutputSend report + hypothesis to ownerSlack
What it does
When a table breaches its freshness SLA, an agent does the first pass of incident triage a human would: it correlates the stalled load with orchestration logs, recent dbt or schema changes, and upstream source health, then writes a structured root-cause draft so the on-call starts with context instead of a blank page.
When to use it
Use it for high-stakes tables where every breach warrants a real post-incident write-up and you want the investigation legwork done before the engineer opens their laptop.
How it works
- 1A freshness-breach webhook fires with the table name and staleness age.
- 2The agent queries Snowflake for the load history, last successful run, and query errors around the gap.
- 3It pulls recent commits touching that model's path from GitHub to spot likely culprits.
- 4Logic weighs the evidence into a leading hypothesis and a confidence level.
- 5It drafts a structured RCA page (timeline, suspected cause, blast radius, next steps) in Confluence.
- 6It posts the report link and hypothesis to the owner in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect HTTP webhookTrigger any URL on agent actions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.