My Shorts-to-Reels Autopilot Thought It Was 2033: One Line Was the Bug
GitHub skipped the job, and when I started it by hand, the log said "today is May 24, 2033. Not publishing."
· 8 views · YouTube video: My Shorts → Reels Autopilot Thought It Was 2033
Watch on YouTube · Subscribe to @PROOFOFDATA
Quick overview
- One line added 40 minutes as 2,400 days, so the tool thought it was May 24, 2033 and refused to post.
- GitHub skipped the scheduled job. A free cron-job.org timer now starts it on time.
- Reels Studio is free and open source. It reposts Shorts as Reels with the same title, hashtags and cover.
- 2,400 days What the code added instead of 40 minutes
- 2033 The year the tool thought it was
- 1 line Code changed to fix the date bug
What happened
The first Reel was scheduled for 5:00 p.m. Nothing went out. GitHub had skipped the scheduled job.
I started it by hand. The log said "today is May 24, 2033. Not publishing." A time offset of 40 minutes (2,400 seconds) was being added as 2,400 days, which pushed the date years into the future.
The fix
Changing one line fixed the date math. The delayed Reel went out at 6:23 p.m.
To stop relying on GitHub's own schedule, a free outside timer (cron-job.org) now triggers the run. Since then, Reels post on time without anyone touching them. The tool was built with Claude Code.
Watch the 30-second Short, then the full video with all 3 problems I hit
FAQ
Why did my GitHub Actions scheduled cron job not run on time?
GitHub's scheduled workflows can be delayed or dropped when its servers are busy, and here the job was skipped completely. The fix was an external trigger: cron-job.org, which is free, calls the workflow at the set time.
Watch on YouTube · Subscribe to @PROOFOFDATA
Topics: coding bug, automation, claude code, github actions, cron job, youtube shorts to instagram reels, instagram reels automation, proof of data


