Every morning, a bot posts a short report to Slack: what moved volume and revenue yesterday, driver by driver. It runs on a GitHub Actions schedule and checks its own numbers before it posts. For a small team, it's a good setup. There's no server to babysit, the logs and secrets live in one place, and anyone on the team can read the run history.
It's also a scheduler with fine print, and nearly all of the fine print is about the morning the report doesn't arrive. Here's what GitHub's documentation says about scheduled workflows, what it means for a daily report, and the safeguards that make up for it.
The fine print
These are all in GitHub's docs for the schedule event, roughly in order of how likely they are to bite.
Scheduled runs can be late, and some never happen. GitHub warns that scheduled runs can be delayed when Actions is under heavy load, that the start of every hour is one of those times, and that under enough load "some queued jobs may be dropped." A dropped run doesn't fail.…