How to diagnose overlapping calendar invites without deleting the wrong events

Start with one reproducible conflict

When several invitations overlap, mass deletion feels like the fastest reset. It also removes the evidence needed to find the cause and can disrupt meetings that the scheduling tool does not own. Begin with one pair of events. Record their local dates, start and end times, calendar names, organizers, and the action each is supposed to represent. Keep that record private.

Distinguish an actual overlap from a missing buffer. A task ending at 10:00 and a meeting beginning at 10:00 do not share minutes, but they still violate a 15-minute separation policy. Diagnose both conditions explicitly. Also check whether the issue exists in the provider calendar itself or only in an application view, where an old local representation may still be displayed.

Confirm identity before calling something a duplicate

Open the event details rather than relying on the calendar tile. Two sessions of a long task may intentionally share a subject. A recurring meeting may have an edited occurrence. An imported invitation may coexist with a separately created task block. These situations need different repairs, even when the visible titles look identical.

Google documents that its event ID and iCalendar UID are different identifiers; recurring occurrences can share an iCalendar UID while having different event IDs. If support needs technical evidence, provide the minimum identifiers through an appropriate private channel. Do not publish calendar feed URLs, invitation links, meeting passcodes, attendee lists, or authorization tokens in a screenshot or public issue.

Sources: Google Calendar Events reference

Check scope, availability, timing, and ownership separately

Work through the layers in order. Scope asks whether the scheduling application can read the calendar containing the competing appointment. Availability asks whether the provider considers the event busy. Timing asks whether both systems mean the same instant. Ownership asks which system is allowed to move or remove each event. Skipping a layer usually turns diagnosis into trial and error.

Google's available-versus-busy setting is independent of an event's label. Check the actual setting, especially for imported holds. Inspect the timezone in both the workspace and the event; a familiar clock time is not enough when travel or daylight-saving transitions are involved. Finally, leave externally organized meetings alone unless you have the appropriate authority and have coordinated the change.

Sources: Google Calendar Events reference

Worked example: a two-hour task inside existing meetings

Consider a fictional Tuesday calendar. A meeting occupies 09:00–10:00, a two-hour task block appears at 09:30–11:30, and another meeting begins at 11:30. Moving the task to 10:15 fixes the first overlap but creates a new one: it would end at 12:15, well into the second meeting. Checking only the start time is therefore insufficient.

With a 15-minute gap on each side, the opening between 10:00 and 11:30 holds only 60 minutes of work. A two-hour session needs another opening. If the next fixed meeting ends at 13:00 and the following one starts at 16:00, a 13:15–15:15 session fits, with more than the minimum separation afterward. This example assumes no other busy events; the actual connected calendar must confirm that assumption.

If no two-hour opening exists before the deadline, make a scope or timing decision. Do not silently shorten a two-hour estimate to make the layout look valid. A smaller independently useful action may be appropriate, but it must represent a real change in the work, not a hidden scheduling shortcut.

Read the connection state before retrying

Repeatedly pressing sync is not a substitute for authorization. In Critical Path, open Settings → Connections and distinguish a connected calendar from one that requires attention. Confirm the expected account and working calendar. If access expired, reconnect through the application. Never paste access tokens into a task, document, chat message, or troubleshooting form.

The application attempts reconciliation on a five-minute schedule. That cadence means an attempt is scheduled, not that every external edit is repaired within five minutes. A provider outage, incomplete read, rejected write, or unavailable replacement window can prevent completion. Google Freebusy responses can include per-calendar errors; those errors are not evidence that the calendar is empty.

Sources: Google Calendar Freebusy query reference

Repair the source relationship, then verify the result

Critical Path tracks provider event identities against task blocks and checks existing placements during reconciliation. Its policy uses a 15-minute minimum gap and sessions no longer than two hours. A missing or invalid block can require a new placement; an application-owned obsolete event can require cleanup. Failed availability checks should leave protected work intact rather than treating the failure as free time.

Use the source task to correct a mistaken allocation, date, or completion state. For an external meeting, coordinate with its organizer. Do not bulk-delete all red events or all invitations from a particular sender. A title or color is not sufficient proof that a specific event belongs to the workspace or should be removed.

1. Capture the single conflicting pair and confirm event ownership privately.
2. Verify account, calendar coverage, timezone, and connected authorization.
3. Correct the source task or coordinate the external meeting change with its owner.
4. Allow a successful synchronization and inspect the final provider calendar.
5. Check the replacement duration and both 15-minute boundaries; confirm any superseded block is no longer occupying the old slot.
6. If the conflict remains, report the narrow example and visible error without exposing unrelated calendar data.

Include late out-of-office changes in the diagnosis

Google exposes out of office as a specific event type, with availability depending on account eligibility. A working-location note is a different concept from an absence. In Critical Path, recognized out-of-office intervals are treated as unavailable during scheduling. When absence is added after task invitations, successful reconciliation must find feasible replacement time before the plan can be trusted again.

Download the checklist below and use it for one incident. Keep the completed copy internal. After repair, look for the underlying pattern: missing calendar coverage, repeated authorization failures, an unrealistic deadline, or duplicate sources creating the same commitment. Fixing that cause is more valuable than repeatedly cleaning up the visible symptom.

Sources: Google Calendar status-event guide

Common questions