DATA OPS
Weekly Unrecoverable-Records Report for Reverse-ETL
Each week, summarizes all rows that exhausted their retries across reverse-ETL syncs, builds an owner-by-owner breakdown from the Snowflake quarantine history.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly report schedule
- ActionQuery exhausted-retry rows from Snowflake quarantineSnowflake
- LogicAggregate by owner + reason, build CSV
- ActionArchive CSV to S3AWS S3
- OutputEmail per-owner unrecoverable digest with CSV linkGmail
What it does
Rows that can never sync automatically still need an owner. This workflow rolls up a week of permanently failed reverse-ETL records from your Snowflake quarantine history, attributes each to the upstream data owner, and produces a clear report of what's unrecoverable and who needs to fix it. It turns a silent backlog into an accountable weekly to-do list.
When to use it
Use it as the reporting layer on top of your self-healing pipelines: the retry and quarantine workflows handle the machine-fixable cases, and this one surfaces the human-fixable remainder on a predictable cadence so nothing rots in quarantine indefinitely.
How it works
A weekly schedule trigger queries the Snowflake quarantine table for rows that exhausted their retry budget in the period. A logic step aggregates them by data owner and failure reason and assembles a CSV of the affected records. The CSV is archived to S3 for the record. A summary email then goes out via Gmail with per-owner counts, the top failure reasons, and a link to the archived file so each team knows exactly which records to repair.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect AWS S3Buckets, objects, signed URLs.
- 3Connect GmailRead, draft, send, label.
- 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
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.
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 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 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…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.