Troubleshooting

Google Calendar Event Updated, But It Still Shows the Old Time?

A fast proof-first workflow for edit/update failures and timezone drift in Calendar tasks.

If your agent says it updated a calendar event but the old time/details still show, don’t spam retries. Use this 4-minute isolate-and-proof flow.

What this usually is

Most cases are one of these: wrong calendar selected, wrong event edited (same title), timezone shift, or stale UI cache in Google Calendar.

Step 1) Lock the Exact Event Identity

Identify the exact event by title + date + start time + calendar name.
If multiple events share the same title, include a unique clue (attendee, location, description text).
Ask the agent to show the event metadata before editing.

Before editing, list the exact target event:
- Calendar name
- Event title
- Current start/end time with timezone
- Event ID (if available)
Then apply the update and show the new start/end time with timezone.

Step 2) Run a Tiny Edit Canary

Change one small field first (for example: add [CANARY] to the title).
Read the event back immediately after edit.
If canary change is visible but time is wrong, you likely have a timezone or all-day/timed mismatch.

Step 3) Force Timezone Proof

Ask for both the input timezone and the stored timezone on the event:

Update this event to:
- Date: 2026-04-07
- Start: 09:00
- End: 09:30
- Timezone: America/New_York
After updating, read it back and print:
- Stored start/end timestamps
- Stored timezone
- Whether the event is timed or all-day

Loop-break rule

If two proofed attempts still write the wrong value, stop retries and escalate with evidence. Repeated blind edits create duplicates and confusion.

High-Friction Edge Cases

Same event title exists multiple times

The agent may edit the wrong one unless you provide date/time/calendar identity. Never rely on title alone.

Recurring series vs one occurrence

Google Calendar can update only this event or the entire series. If the wrong scope is chosen, it can look like your update was ignored. Require the agent to state exactly which scope it edited.

All-day vs timed event mismatch

Updating an all-day event with timed fields can produce unexpected display shifts. Force the agent to confirm event type.

Organizer/permission mismatch

If you are not the organizer (or only have limited access), edits may partially apply or fail silently. Ask the agent to confirm your effective permission level on that calendar/event.

Google Calendar UI looks unchanged

Sometimes the browser view is stale. Hard refresh once, then open event details. Trust API/read-back evidence over cached list view.

Wrong calendar got edited

Many users have Personal + Work calendars with similar events. Require explicit calendar name in every edit command.

Escalation Packet (Copy/Paste)

Issue summary: Calendar event update says success but old value remains
Calendar name:
Event title:
Original date/time + timezone:
Requested new date/time + timezone:
Timed or all-day:
Recurring scope (single event or full series):
Canary edit used:
Read-back result after update:
Permission level (owner/editor/viewer):
Surface used (dashboard/Discord/etc):
Timestamp + timezone:
Any duplicate events created:

Security note

Redact attendee emails and private meeting links before sharing support evidence.