A sync is delayed or incomplete

Check source and destination independently

Open the original event at the provider and confirm that the expected change exists there. Then inspect the destination calendar, not just an app that may have its own cached view. Verify that you are comparing the same source and destination connection.

Inspect the connection

Check whether it is active or paused, whether either account needs reconnect, and whether the destination is still writable. A provider outage, throttling or a processing backlog can delay work even if the local event was saved successfully.

Compare the allowed representation

Busy-only may intentionally remove the title or details. A policy change can change which fields appear. Do not classify missing descriptions as a sync failure until you have checked the connection’s content policy.

Avoid compounding the problem

Do not repeatedly delete and recreate the connection or manually clone the event into the destination. That can produce overlapping ownership and make diagnosis harder. Keep the original reference, note the time of the last change and contact support with a redacted example.

For room feeds and sources, distinguish polling delay from booking confirmation. A stale free/busy view cannot establish that a room accepted a reservation.