Event Sync Issues
External events from Google Calendar or Microsoft Outlook are not showing up in PrimeCalendar, or they showed up and now some are missing or duplicated. This page covers the most common causes and their fixes.
Events from an external calendar are not showing up
Why it happens: The sync account is either disconnected, the OAuth token has expired, or the initial sync has not yet completed after connecting the account.
Fix:
- Go to Settings → Calendar Sync.
- Check the status indicator next to your Google or Microsoft account.
- If it shows a warning or error icon, the connection needs to be re-established. Click Reconnect and complete the OAuth flow again.
- If it shows "Connected", trigger a manual refresh by clicking Sync now.
- Wait 30–60 seconds and reload the calendar. External events are tagged with a small sync indicator in the event card.
If the status shows "Connected" and a manual sync completes without error but events still don't appear, check that the correct calendars are selected in the sync settings. Each external account lets you choose which sub-calendars to include.
Sync ran but only some events appeared
Why it happens: By default, PrimeCalendar fetches events within a rolling window (typically the past few weeks through the next few months). Events far in the past or future may be outside the sync window on the initial import.
Fix:
- Trigger a manual sync from Settings → Calendar Sync → Sync now.
- If you need to import a specific historical event, check whether your plan includes extended history sync.
- All-day events and multi-day events sometimes render differently in week view — switch to month view to confirm they are not already present.
Duplicate events after syncing
Why it happens: Duplicates appear when the same event is synced twice — usually because the account was disconnected and re-added, which causes a fresh full sync to run alongside a still-active partial sync. This is a known edge case when switching accounts.
Fix:
- Go to Settings → Calendar Sync and disconnect the affected account.
- Wait a minute for the cleanup process to run (duplicate synced events are removed when an account is disconnected).
- Reconnect the account and allow the fresh initial sync to complete.
If duplicates persist after reconnecting, verify you have not added the same external account email address twice under different entries. Each unique provider + email combination should appear only once in the sync list.
Events disappeared after they were previously visible
Why it happens: This typically happens when the external OAuth token expired and the background sync silently stopped. The events remain visible until a reload, after which they may disappear because the sync connection is broken.
Fix:
- Go to Settings → Calendar Sync.
- If the account shows a disconnected or error status, click Reconnect.
- Complete the OAuth flow. Sync resumes and your events reappear within 1–2 minutes.
Plan limit: "You have reached your sync account limit"
The Free plan supports one external sync account total across all providers. If you need to connect both a Google account and a Microsoft account simultaneously, you need a paid plan.
Fix:
- Disconnect one account if you only need one provider at a time.
- Upgrade your plan at Settings → Subscription to unlock multiple sync accounts.
API integrations that hit this limit will receive HTTP 403 with { "code": "PLAN_LIMIT_REACHED", "limitKey": "max_calendar_sync_providers" }.
Sync is working but events show the wrong timezone
Why it happens: Events from external calendars carry their original timezone. If your PrimeCalendar profile timezone does not match the timezone of your external events, times can appear offset.
Fix:
- Go to Settings → Profile.
- Confirm your Timezone is set to your local timezone.
- Trigger a manual sync from Settings → Calendar Sync.
Still stuck?
- Check Settings → Calendar Sync for any error messages on the account card.
- Review the Google Sync Problems or Microsoft Sync Problems pages for provider-specific issues.
- Contact support if reconnecting doesn't resolve the issue.