<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: haruki</title>
    <description>The latest articles on DEV Community by haruki (@quiet_pipelines).</description>
    <link>https://dev.to/quiet_pipelines</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4246334%2F798de882-ff07-414f-9ef2-f4811161df68.png</url>
      <title>DEV Community: haruki</title>
      <link>https://dev.to/quiet_pipelines</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/quiet_pipelines"/>
    <language>en</language>
    <item>
      <title>My YouTube automation kept "running" for almost 6 months. The bot made 1,376 commits. Zero uploads, and I had no idea.</title>
      <dc:creator>haruki</dc:creator>
      <pubDate>Sun, 15 Nov 2026 17:42:04 +0000</pubDate>
      <link>https://dev.to/quiet_pipelines/my-youtube-automation-kept-running-for-almost-6-months-the-bot-made-1376-commits-zero-uploads-11c5</link>
      <guid>https://dev.to/quiet_pipelines/my-youtube-automation-kept-running-for-almost-6-months-the-bot-made-1376-commits-zero-uploads-11c5</guid>
      <description>&lt;p&gt;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".&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;4 were expired or revoked credentials&lt;/li&gt;
&lt;li&gt;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)&lt;/li&gt;
&lt;li&gt;5 were my own code or config&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So 9 of 14 had nothing to do with my code. The world moved and my pipeline stayed still.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Other things I learned the hard way that night:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;I asked the agent to delete temp files matching &lt;em&gt;probe&lt;/em&gt;. 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.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;What I am changing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Check outcomes, not exit codes. "Did a video actually appear on the channel today" is the only health check that matters.&lt;/li&gt;
&lt;li&gt;Keep an expiry ledger: every token, key, free tier and model name, with the date it dies.&lt;/li&gt;
&lt;li&gt;Alerts go somewhere I actually look, and the alerting path must not depend on the thing it monitors.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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?&lt;/p&gt;

&lt;p&gt;Note: I wrote this post with AI assistance. The incident, numbers and fixes are from my own pipeline.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>debugging</category>
      <category>githubactions</category>
      <category>python</category>
    </item>
  </channel>
</rss>
