When Claude sets a reminder for the wrong time

You asked for 8am and the phone rang at 3am. Before assuming the reminder is broken, know that a call landing at the wrong hour is almost always one thing: a time-zone mismatch. ReminderIt schedules against IANA time zones, and if the wrong one was attached, every call for that reminder is offset. The fix is quick once you know where to look.

Why the time drifts

ReminderIt stores each reminder against a specific IANA time zone, such as Europe/London or America/New_York, so a time only means something once its zone is known. If a reminder was created with the wrong zone, or with none confirmed, the hour you asked for is interpreted somewhere else and the call fires offset from your local clock.

This is why a reminder can look perfectly correct in the wording and still ring at the wrong moment. The number is right; the zone behind it is not.

Confirm your time zone

Start by pinning down your own zone as an IANA string. It is not a city guess or a UTC offset but a named zone like Asia/Kolkata or America/Los_Angeles. If you are unsure which one you are in, that ambiguity is often the very cause of the problem.

Ask Claude to read back the reminder: "What time zone is my morning call set to?" It runs get_reminder or list_reminders and tells you the stored zone. Compare that against where you actually are.

Fix it with update_reminder

Once you know the right zone, correcting it is one sentence. Say "Change my 8am medication call to Europe/London" and Claude runs update_reminder to reset the zone while keeping the time and wording. There is no need to delete and rebuild the reminder.

If both the time and the zone were off, fix them together: "Set my medication call to 8am Europe/London." Claude applies both in a single update.

Verify with list_upcoming

Never trust a time fix blind. Ask "When does my medication call next ring?" and Claude runs list_upcoming, which shows the next occurrence in your corrected local time. Read it back against your watch to confirm the offset is gone.

If you want absolute certainty before the real thing, "Ring me now to test it" uses test_call so you can hear the call immediately, though that does draw one from your monthly allowance.

A note on daylight saving

Using a proper IANA zone rather than a fixed offset is what keeps you right across daylight saving changes. A named zone like Europe/London knows when the clocks move, so an 8am call stays at 8am local through spring and autumn without you touching it.

That is exactly why ReminderIt asks for the zone rather than a bare offset. If you ever set a reminder with a fixed offset in mind, switch it to the named zone so DST is handled for you.