DATA OPS
Detect missing daily source extracts and auto-file a Linear ticket
Each morning this checks whether every expected upstream source delivered yesterday's data into Snowflake.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning cron after source loads
- ActionQuery recent load dates per sourceSnowflake
- LogicIdentify sources missing yesterday
- ActionAssemble ticket body per gap
- OutputCreate a Linear ticket per gapLinear
What it does
Finds gaps in inbound data. It queries Snowflake landing tables for the set of distinct load dates per source over the recent window, determines which sources are missing yesterday's partition entirely, and opens one Linear ticket per gap. Each ticket carries the source, the missing date, and when that source last delivered, so triage starts with context instead of a mystery.
When to use it
Use it when upstream vendors or internal jobs occasionally just don't deliver, and a silent missing day quietly corrupts a downstream metric days later. This surfaces the gap the next morning as a tracked, assignable issue.
How it works
- 1A morning cron fires after all source loads should have landed.
- 2A Snowflake query returns recent load dates and last-seen timestamps per source.
- 3A logic step compares expected sources against those that delivered yesterday and lists the gaps.
- 4For each missing source, a ticket body is assembled with the gap date and last-seen time.
- 5A Linear issue is created per gap and labeled for the data engineering team.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.