Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My calendar integration keeps creating duplicate events

Short answer

Duplicates appear when a sync cannot tell that an event is already there. Google's sync guide says to store a sync token and, when it answers 410, to wipe local data and run a full sync. An import needs the event's iCalUID, and recurring events share one iCalUID across different ids.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The same booking or meeting shows twice or three times in my calendar.
  • Duplicates appear in a batch after the connection was reset.
  • A recurring meeting has extra copies.
  • Double bookings happen because the copy blocks a slot or hides the real one.
  • Deleting a duplicate brings it back.

Why does this happen?

  1. A full sync runs again on top of old data

    Google's sync guide describes an initial full sync followed by incremental syncs that use a stored sync token. If the server answers 410, the token is no longer valid, and the client must clear its stored data and run a full sync. A tool that runs the full sync again without clearing what it created before will add every event a second time.

  2. Deleted entries are part of the answer

    Google states that incremental sync results always contain deleted entries, so the client can remove them locally. A tool that ignores them keeps showing events that were removed, and may recreate them.

  3. Imported events need a stable identity

    Google states that the import method adds a private copy of an existing event to a calendar and that the iCalUID must be supplied. The iCalUID identifies an event across calendar systems and is not the same as its id. A tool that cannot match an incoming event to one it already holds, treats it as new.

  4. Recurring events share one identity

    Google states that all occurrences of a recurring event share one iCalUID but have different ids. A tool that matches only on one of the two can create extra copies, or merge occurrences that are different.

  5. Two systems both push changes

    When a booking tool, a CRM and the calendar each write to the other, an event one of them creates can come back as a new event from another.

What can I do about it today?

  1. Stop manual reconnectingResetting the connection repeatedly can trigger more full syncs and more duplicates.
  2. Note which events are doubledWrite down a few examples: the title, the time, which calendar and when each copy appeared.
  3. Find out which tools write to this calendarList every booking page, CRM, phone app and automation connected to it. Duplicates usually have two writers.
  4. Do not bulk delete yetDeleting copies by hand can send deletions back through the sync and remove real events. Wait until the cause is known.
  5. Send the examples to your developerDates of the first duplicate, the tools involved and any recent change to the connection.

When should I bring someone in?

  • Duplicates return after you delete them.
  • Real customer bookings are hidden or doubled and clash with each other.
  • More than one system updates the same calendar.

How do I handle it?

  1. Trace one duplicate to its sourceI follow a single doubled event through the tools that touch the calendar until I find which one created each copy.
  2. Give every event one identityEvents are matched on a stored identifier, using the event id or the iCalUID, so a re-run updates the existing event instead of adding another.
  3. Store the sync token properlyThe sync token is saved, and a 410 answer is handled the way Google describes: clear what was held, then run a full sync.
  4. Choose one source of truthI settle which system owns each kind of event, so the others only read it.
  5. Clean up on a copyExisting duplicates are listed first and removed only after you have approved the list.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

What does 410 mean in Google Calendar sync?

Google states it means the server invalidated the sync token, for example through expiry or changes to access. The client must clear its stored data and run a full sync.

Why do recurring meetings duplicate more?

Google states that all occurrences share one iCalUID but have different ids, so a tool that matches on a single value can get it wrong.

Can the duplicates be removed automatically?

Yes, once the cause is fixed. I list them first and delete only the ones you confirm.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.