Know how your dbt jobs really behaved this week
Every Monday, WebRun signs in to dbt Cloud, reads the last seven days of run history across your jobs, works out the success rate, the average and worst run durations, and which models failed most often, writes a dated scorecard page into Notion, and texts the on-call engineer the headline through Twilio.
- 7-day free trial
- Under $0.01 per run
- Cancel anytime
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.getdbt.comin a real browser with your saved login - no setup, no API keys. -
1
dbt Labs - read the week's run history
WebRun opens dbt Labs to read the week's run history. - Sign in to dbt Cloud and open run history for the last seven days
- Record every run with its job, environment, status, and duration
- Work out the success rate per job and the average and longest durations
- Note which models or tests failed more than once during the week
Done when Every run in the last seven days is captured with status and duration.
-
2
Notion - write the run health scorecard
WebRun opens Notion to write the run health scorecard. - Create a dated run health page in your data team space
- Show overall success rate, total runs, and total failures at the top
- Add a per-job table with success rate, average duration, and longest run
- List repeat offenders: the models and tests that failed more than once
- Compare each figure with last week so a slow drift is visible
Done when The Notion scorecard is complete with per-job numbers and a week on week comparison.
-
3
Twilio - text the on-call the headline
WebRun opens Twilio to text the on-call the headline. - Text the on-call number you registered with the week's success rate and failure count
- Name the single job with the worst reliability and the slowest run
- Send only to your own registered internal numbers, never to a customer or a stakeholder
- Queue any message to a number outside that list for a person to approve
Done when The on-call engineer has this week's headline by text.
How do I track dbt job reliability week over week?
WebRun signs in to dbt Cloud every Monday and reads the last seven days of run history across your jobs, calculating success rates, average and worst durations, and repeat failing models. It writes a dated scorecard into Notion and texts the on-call engineer the headline through Twilio.
- Reliability is measured weekly, not guessed at
- Slow jobs surface before they miss a deadline
- Repeat failing models are named instead of re-run and forgotten
Built for analytics engineers · data platform teams · data leads · on-call engineers
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Who can it text?
Only the internal on-call numbers you register. Any message addressed to a number outside that list is queued for a person to approve, so no stakeholder or customer is texted unreviewed.
Will it trigger or cancel a dbt job?
No. WebRun reads run history only. It never starts a run, cancels one, edits a job schedule, or changes an environment or a model.
How is this different from a failure alert?
A failure alert fires on one broken run. This is the weekly pattern: success rate per job, average and worst durations, and the models that failed more than once.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.