Why syncing might be delayed

2calendars is designed to mirror events within seconds of a change. However, there are situations where syncing may take longer than expected.

Common causes of delays

Google API latency

2calendars relies on Google Calendar APIs to detect changes and write mirrored events. Occasionally, Google may be slow to report changes or process write requests. This is outside our control and usually resolves on its own within minutes.

Rate limiting

Google imposes rate limits on API requests. If you have many connections or a high volume of calendar changes in a short period, some requests may be queued and processed with a slight delay.

Service maintenance

During planned maintenance or updates, syncing may be briefly paused. We aim to keep any interruptions minimal.

Network or infrastructure issues

Temporary network issues between our servers and Google’s APIs can introduce delays. These are typically resolved automatically.

What is normal

• Most events sync within a few seconds of being created or modified.
• During periods of high activity, syncing may take up to a few minutes.
• If syncing is delayed beyond 15 minutes, there may be an underlying issue worth investigating.

What to do if delays persist

1. Check your connection health status on the 2calendars dashboard.
2. Verify that your Google account is still authorized and connected.
3. Look for any health notification emails that may indicate a problem.
4. If the issue continues, contact us at [email protected] with details about which connection is affected and when the delays started.

Note that references to “real-time” syncing describe intended behavior under normal conditions. Syncing is not guaranteed to be instantaneous in all circumstances.