All templates

Automated BigQuery Failure and Cost Alerts

Every morning, WebRun opens BigQuery in the Google Cloud console, checks every scheduled query for failed or skipped runs, reads the job history for yesterday's bytes processed and the heaviest queries, posts a digest to your data channel in Slack, and sends a Telegram alert when a scheduled query failed or processing went past your daily budget.

Runs on WebRun · Strict Lockdown policy
Every day at 7:00 AM WebRunorchestrates each step
1 BigQuery check scheduled queries and job history
2 Slack post the morning data digest
3 Telegram alert on failures and budget breaches
In short

How do I know when a BigQuery scheduled query fails overnight?

WebRun opens BigQuery in the Google Cloud console every morning, checks every scheduled query for failed or skipped runs, and reads yesterday's bytes processed and heaviest queries. It posts a Slack digest to your data channel and sends a Telegram alert only when a schedule failed or processing passed your budget.

  • A failed overnight schedule is known before the first dashboard is opened
  • Stale tables are named so nobody reports on old data
  • Processing costs are compared against budget every single morning

Built for data engineers · analytics teams · data platform owners · BI developers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens console.cloud.google.com/bigquery in a real browser with your saved login - no setup, no API keys.

  2. 1
    BigQuery - check scheduled queries and job history
    console.cloud.google.com
    WebRun in BigQuery: check scheduled queries and job history
    WebRun opens BigQuery to check scheduled queries and job history.
    • Open BigQuery in the Google Cloud console and go to Scheduled queries
    • Check the last run of every schedule and capture any that failed, were skipped, or have not run since their expected time
    • Record the error message on each failure so the cause travels with the alert
    • Open Job history and read yesterday's completed jobs, capturing the total bytes processed and the ten heaviest queries with their user and destination table
    • Compare yesterday's total processing against your daily budget and against the previous 7 day average
    • Read only. WebRun never runs an ad hoc query, so the check itself costs nothing to process

    Done when Every scheduled query has a known last-run state and yesterday's processing totals are captured.

  3. 2
    Slack - post the morning data digest
    slack.com
    WebRun in Slack: post the morning data digest
    WebRun opens Slack to post the morning data digest.
    • Post a digest to your data channel with the count of scheduled queries that ran, failed, or were skipped
    • List yesterday's total bytes processed next to the 7 day average
    • Name the heaviest queries with the user who ran them and the destination table
    • Note any table that did not refresh because its scheduled query failed, so downstream users know the data is stale

    Done when The data channel has the morning digest with run counts and processing totals.

  4. 3
    Telegram - alert on failures and budget breaches
    telegram.org
    WebRun in Telegram: alert on failures and budget breaches
    WebRun opens Telegram to alert on failures and budget breaches.
    • Send an alert only when something needs attention: a failed or skipped scheduled query, or processing past your daily budget
    • Give each failure the schedule name, the time, and the error message
    • For a budget breach, state yesterday's total, the budget, and the query that consumed the most
    • Stay silent on a clean morning so the alert keeps its meaning

    Done when You have an alert for every failure and budget breach, and silence when there are none.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
console.cloud.google.com/bigquery
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
Data digest · Slack
OutputWhat each run produces - A morning Slack digest of scheduled query runs and yesterday's processing totals with the heaviest queries, plus a Telegram alert for failures and budget breaches.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it run queries and add to my bill?

No. WebRun reads the Scheduled queries and Job history pages in the console. It does not run ad hoc SQL, so the check adds nothing to your processing costs, and it never creates, edits, or deletes a table or dataset.

Will it rerun a failed scheduled query?

No. A failure is reported with its schedule name, time, and error message, and a person decides whether to rerun it. WebRun never triggers, pauses, or edits a scheduled query.

Does it alert me every single morning?

Slack gets a digest every morning. Telegram stays silent unless a scheduled query failed or processing went past your daily budget, so an alert on your phone always means something needs attention.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.