Automated Modal Daily Job Digest
Every morning, WebRun opens the Modal dashboard, reads how every scheduled function and job ran overnight, posts a digest of completions and failures to Telegram, and sends a Twilio text if any job actually failed, so the team starts the day knowing exactly what ran.
How do I get a daily summary of my Modal compute jobs?
WebRun reads every Modal function and job run from overnight, every morning, noting what completed, what failed, and how long each took. It posts a digest to Telegram so the team starts the day with a clear picture, and sends a Twilio text if anything actually failed, so a broken job gets same morning attention instead of getting buried in a dashboard.
- Every overnight job run gets a same morning digest
- Failed jobs get a same morning text, not a buried log line
- The team starts the day knowing exactly what needs attention
Built for ML engineers · data science teams · AI startups running batch jobs · platform engineers
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
modal.comin a real browser with your saved login - no setup, no API keys. -
1
Modal - read how jobs ran overnight
modal.com
WebRun reads how jobs ran overnight in Modal. - Open the Modal dashboard and read every function and job run from overnight
- Note which completed, which failed, and how long each took
- Capture the error summary for anything that failed
Done when Every overnight job run is accounted for.
-
2
Telegram - post the daily digest
telegram.org
WebRun posts the daily job digest in Telegram. - Post a daily digest listing completed and failed jobs
- Show run time and any error summary
- Send it once each morning, not per job
Done when The team has this morning's job digest in Telegram.
-
3
Twilio - text about any failed job
twilio.com
WebRun texts about any failed job through Twilio. - Send a text only if at least one job failed overnight
- Name the failed job and a one line error summary
- Leave debugging and rerunning the job to the engineer
Done when A failed job gets a same morning text, not just a digest line.
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
Does it rerun a failed job automatically?
No. WebRun only reads job status and reports it. Rerunning or debugging a failed job stays a manual step the engineer takes.
Will I get a text for every job that ran?
No. The Telegram digest covers every job. The Twilio text is reserved for mornings when at least one job actually failed.
Does it show how long jobs took to run?
Yes. The digest includes each job's run time, so you can spot one that's running slower than usual even if it didn't fail outright.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.