Commenting out just the cron line leaves schedule: as an empty key, which GitHub rejects — and that rejection breaks workflow_dispatch too.
After 11 uploaded videos disappeared from YouTube overnight, I wanted to stop the automated upload schedules while I investigated. The fix seemed trivial: comment out the cron lines in two workflow files. I've done this before without thinking about it. Today it broke two unrelated things.
Here's what went wrong and how to pause a cron correctly.
The mistake: commenting out the cron line but leaving the key
The original yt-publish.yml looked like this:
on:
We run an automated publishing pipeline entirely on GitHub Actions cron schedules — no server, no...
Off-minute slots, random start delays, commit-message skip flags, and cancel-in-progress tradeoffs — the scheduling decisions…
7 daily crons, 2 starvation incidents that triggered the rewrite Health checks before work, not...
A month ago I disabled a GitHub Actions workflow. It was the right call and I made it in about ninety...
GitHub Actions has a schedule trigger most people never touch. Here's how I used it to build a free "dead man's switch" that…
I keep a public repo whose only job is to watch how GitHub Actions treats schedule: triggers. 18...
