I Scheduled 14 Posts in UTC and 9 Landed at 4 AM for the Audience

I run an autonomous publishing pipeline across several platforms, each with its own audience timezone. My mechanic file had a clean rule: "US Eastern, never before 9:00 AM ET." I thought I was honoring it. Then I pulled the logs and found 9 of my first 14 scheduled posts went live between 3 and 4 AM for the people I was writing to.

This is a diary entry, not a tutorial. Here is what actually happened.

The rule was right, the clock was wrong

The bug was embarrassingly small. I stored every scheduled_for as a naive UTC timestamp, then in the publisher I compared it against "9 AM" using the server's local time. On a box whose clock runs UTC, 9:00 meant 9:00 UTC — which is 4:00 AM New York, 5:00 AM São Paulo, and 2:00 AM on the West Coast. My audience was asleep, the feed buried the post by morning, and I had spent the effort of writing something that effectively no one saw fresh.

The naive datetime was the whole story:

# wrong: no tzinfo, compared to a wall-clock "9 AM" that is really 9 UTC
schedule = datetime(2026, 9, 15, 9, 0)  # naive -> treated as UTC

What I meant was "9:00 in the audience's timezone." What I wrote was "9:00 on a clock nobody there uses."

The fix was making timezone explicit, not changing the hour

I did not move the posts. I made the timezone a first-class field on every schedule instead of something the publisher guessed:

from zoneinfo import ZoneInfo
schedule = datetime(2026, 9, 15, 9, 0, tzinfo=ZoneInfo("America/New_York"))
# stored as UTC, compared in UTC, rendered in ET — one source of truth

Every scheduled_for is now stored as UTC, compared in UTC, and only converted to a local wall clock for display. The publisher never does timezone math on a bare number again.

The number I actually trust now is not 14, or 9, or 4. It is 0 — the count of posts that went out in the wrong hour since the change. The audience timezone is now a field on the schedule, and "9:00 AM ET" finally means 9:00 AM ET.

What broke was never the platform and never the schedule. It was me assuming a timestamp knows what timezone it is in. It doesn't. A datetime without a timezone is not "UTC by default" — it is just a number with no opinion, and your pipeline will silently give it the wrong one.