DATA OPS
Source Feed Arrival Deadline Watchdog: Escalate the Late Upstream
Watches for an expected source file to land in cloud storage by its daily deadline; if it's missing, it escalates to the data team and the upstream vendor, then logs the SLA miss.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule after feed deadline
- ActionCheck for expected file in S3AWS S3
- LogicOn-time, late, or missing?
- ActionPage on-call if missingPagerDuty
- ActionEmail upstream vendor contactGmail
- OutputLog arrival outcome to SLA tableSnowflake
What it does
Guards the front of the pipeline rather than the warehouse end. It confirms a vendor or partner dropped the expected file into storage by the contractual deadline. A no-show is caught and escalated to both your team and the upstream provider before downstream loads even start.
When to use it
Use it when your pipeline depends on an external feed that must arrive by a set time — a daily partner export, a finance extract, a third-party data drop — and a late or missing file should trip an alert, not a silent empty load.
How it works
- 1A schedule fires shortly after the feed's contractual deadline.
- 2List the expected prefix in the S3 bucket and check for today's file by name and minimum size.
- 3Logic decides arrived-on-time, late, or missing.
- 4If missing past the grace deadline, open a PagerDuty incident for the data on-call.
- 5Email the upstream vendor contact with the expected file and deadline missed.
- 6Append the arrival outcome (on-time, late, missing) to the feed SLA log.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GmailRead, draft, send, label.
- 4Connect SnowflakeWarehouses, queries, shares.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.