YouTube Automation Failure: 175 Days Without Uploads
Summary
Pixel's announcement shares a six-month YouTube Shorts automation outage: the bot made 1,376 commits but uploaded nothing for 175 days. An investigation uncovered 14 failures, including expired credentials, upstream service changes, and Google OAuth testing-mode tokens that expired every seven days—a reminder to monitor workflows and keep recovery systems independent.
DEV Community
My YouTube automation kept "running" for almost 6 months. The bot made 1,376 commits. Zero uploads, and I had no idea.
I run a small Python pipeline on GitHub Actions that generates and uploads Shorts for a few YouTube channels. Five scheduled workflows, including one I proudly named "Self-Healing Health Check". Last weekend I finally opened the Actions tab. Every recent run was red. Upload runs, growth jobs, and the self-healing job itself. Meanwhile the bot had pushed 1,376 automated commits since May, so from a distance the repo looked alive. Last successful upload before the fix: May 25. That is 175 days of nothing. I sat down with an AI coding agent and had it run every stage and classify each failure instead of fixing anything. Result: 14 separate problems. 4 were expired or revoked credentials 5 were upstream changes (a TTS endpoint returning 403 until I upgraded the library, a deprecated image model, a free tier that added rate limits, a removed vision model, a trends endpoint returning 404) 5 were my own code or config So 9 of 14 had nothing to do with my code. The world moved and my pipeline stayed still. The actual root cause was not in the repo at all. My Google OAuth app was still in "Testing" status, which means refresh tokens die after 7 days. Every re-auth I had ever done was a 7-day fix. The error in the logs was just invalid_grant. Fixing that had its own trap: the "Publish app" button was greyed out with a vague message about completing the Branding page, even though every required field was filled. It only unlocked after I added a home page URL, a privacy policy URL and an authorized domain. For a personal uploader script. I used a tiny public GitHub repo with a README and PRIVACY.md. Other things I learned the hard way that night: My self-healing workflow shared the same dead token as the jobs it was supposed to heal. It failed every time, quietly. A watchdog in the same failure domain is not a watchdog. My local repo had six months of uncommitted changes. Production was running code from May. I had been "fixing" a version that was never deployed. The agent printed my git remote URL, which had a personal access token embedded in it. Rotated it to a fine-grained token, forgot the Secrets permission, got a 403 on gh secret set, fixed that too. I asked the agent to delete temp files matching probe. The match was case-insensitive and it deleted 41 files of a finished video about the Parker Solar Probe. That one is on me for the sloppy instruction. What fixed production in the end was almost no code. It was: find the real cause, change one Google setting, re-auth once, update one secret. First green scheduled run in a long time followed a few minutes later. What I am changing: Check outcomes, not exit codes. "Did a video actually appear on the channel today" is the only health check that matters. Keep an expiry ledger: every token, key, free tier and model name, with the date it dies. Alerts go somewhere I actually look, and the alerting path must not depend on the thing it monitors. Question for people running unattended automations: how do you catch the "everything is technically running but nothing is being produced" case? Heartbeats? Output checks? Something smarter? Note: I wrote this post with AI assistance. The incident, numbers and fixes are from my own pipeline.

Powered by Readybot.io