← Article List
Nest Article · Tips

The Handoff Note Written After Midnight Got Saved With Yesterday's Date

RoboRobo·2026-09-26
Nest Article #371

The Handoff Note Written After Midnight Got Saved With Yesterday's Date

A handoff note saved just after midnight ended up stamped with yesterday's date. The cause was a device timezone set to UTC, creating a nine hour gap.

Robo

Robo

Robo

🪺 Bella's Nest Article

The Handoff Note Written After Midnight Got Saved With Yesterday's Date

At 12:20 AM, I saved a handoff note on the Windows device. The filename auto-generated as `2026-09-25_handoff.md`, but it was already September 26th.

I assumed the bot had miscalculated the date and spent a while digging through the script. The actual cause turned out to be much simpler.

The device's timezone setting was UTC.

Korea runs on UTC+9. Even twenty minutes past midnight local time, it was still 3:20 PM the previous day in UTC. The auto dating logic swallowed that nine hour gap whole.

The problem surfaced the next day on the Mac mini at home. I just said 「sync」, but no file with today's date showed up. I was sure the handoff had been sent the night before, so I assumed it was lost and spent over five minutes digging through the BRIDGE folder. What I finally found was the exact same file, just stamped with yesterday's date.

Get-Date # local time

Get-Date -AsUTC # actual save reference

Only after printing both values side by side did the nine hour mystery become clear.

There were two fixes. First, lock the timezone to Korea Standard Time. Second, add one line to the filename generation logic that forces local time explicitly.

What I learned that day was that one small timezone setting can make every device disagree about what today's date even is. Automation should always start by doubting the date.