DATA OPS
Auto-Resolve Recovered Freshness Tickets
Polls open data-freshness Linear tickets and, when the underlying BigQuery model has reloaded fresh data, closes the ticket with a recovery note so stale alerts don't pile up…
How it runs
The automated pipeline, trigger to output.
- Trigger30-minute reconciliation
- ActionList open freshness ticketsLinear
- ActionCheck model current freshnessBigQuery
- LogicKeep tickets now within SLA
- ActionResolve ticket with recovery noteLinear
- OutputPost recovery summary to SlackSlack
What it does
Closes the loop on freshness incidents. It checks every open freshness ticket in Linear against the live state of its BigQuery model; when the table has caught up and is fresh again, it resolves the ticket automatically with a comment noting recovery time and total downtime, so the backlog reflects reality.
When to use it
Use it alongside any sentinel that opens freshness tickets. Many staleness incidents resolve themselves once a stuck pipeline retries, and without this the tickets linger and erode trust in the alerting. It keeps the Linear board clean.
How it works
- 1A 30-minute schedule triggers the reconciliation.
- 2It lists open Linear tickets tagged as freshness incidents.
- 3For each ticket it queries BigQuery for the referenced model's current latest-partition timestamp.
- 4A filter keeps only tickets whose model is now within its freshness SLA again.
- 5It resolves each recovered ticket in Linear with a comment recording downtime duration.
- 6It posts a short recovery summary to the data-ops Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
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.