A “ghost event” in Google Calendar is a deleted entry that continuously reappears on your schedule. This persistent looping occurs when an external sync client (such as Apple Calendar, Microsoft Outlook, or a CRM tool) holds a cached local copy of the event and pushes it back to Google’s servers during routine sync cycles. It can also stem from corrupted offline browser data or orphaned secondary calendar subscriptions. Clearing the event directly through the browser interface, emptying the calendar Trash, and resetting active third-party connection tokens resolves the issue.
Fast-Fix: The 45-Second Solution
Ghost events occur when third-party calendar integrations or local cache sync loops re-upload deleted entries to Google’s cloud servers. To fix this, log into calendar.google.com in a web browser, delete the event, empty your calendar Trash bin, and temporarily revoke third-party app permissions under your Google Account security settings. Risk: Low (Causes schedule clutter; no account data lost).
Quick Risk Snapshot
- Severity: Low (Creates schedule confusion and potential double-booking, but does not impact account security or file integrity)
- Safe to Modify?: Yes (Deleting the entry on the primary server will not corrupt valid surrounding events)
- Primary Cause: Third-party calendar client (Apple Calendar/Outlook) pushing cached local events back to Google via CalDAV
- Rare Cause: Corrupted offline storage state in Google Calendar web app or orphaned meeting delegates
Low Risk vs. High Risk Paths
- Low-Risk Path (Local App Sync Loop): The ghost event only reappears after a specific mobile app or desktop calendar client syncs. Unlinking the external app or clearing its cache breaks the loop immediately.
- High-Risk Path (Orphaned API Integration or Shared Calendar Delegate Loop): The ghost event constantly regenerates across all web and mobile views even when external devices are offline. This points to an automated third-party API script (such as a scheduling tool) or a shared calendar delegate with mismatched sync rights.
What This Is Confused With
- Ghost Events vs. Declined Invitations: Ghost events are deleted entries that reappear. Declined invitations remain visible on your grid as outlined or faded boxes because your display settings are set to show declined events. For declined invite visibility, see “Declined” events still showing up in view.
- Ghost Events vs. Third-Party Duplicate Entries: Duplicate entries create two or three identical side-by-side blocks for a single meeting. Ghost events involve a single stubborn entry that refuses to stay deleted. For duplicate entry glitches, see “Duplicate events” syncing with 3rd Party Apps.
What To Do Right Now
- Delete via Web Browser Only: Log directly into
calendar.google.comon a computer. Do not attempt deletion from a mobile app or desktop mail client while troubleshooting. - Empty Calendar Trash: In Google Calendar on the web, click the gear icon (Settings) > Trash, click Empty trash, and confirm deletion. If an event remains in the Trash bin, sync clients can sometimes pull it back.
- Revoke Third-Party App Permissions: Go to
[myaccount.google.com/permissions](<https://myaccount.google.com/permissions>), locate third-party calendar apps or sync services, and click Remove Access to sever the sync bridge pushing the ghost entry. - Disable Offline Calendar Access: In Google Calendar settings on web, navigate to General > Offline, and uncheck Turn on offline calendar to clear corrupted local storage handles.
Hard-Stop Triggers
Escalate to your Google Workspace administrator if you experience any of the following:
- The ghost event belongs to a user account that was recently deleted or suspended by your organization.
- Deleting the entry triggers an API error or infinite loading spinner inside the Google Calendar web interface.
- The event was created by an automated system account across hundreds of domain calendars simultaneously.
What an Admin Will Check
When escalating persistent ghost events, a Google Workspace administrator will perform the following diagnostics:
- Google Workspace Audit Logs: Reviewing Calendar audit logs (
Reporting>Audit and investigation>Calendar log events) to identify the exact IP address, user agent, or OAuth application token responsible for re-creating the deleted event. - OAuth Token Revocation: Force-revoking third-party sync tokens across the domain for affected user accounts.
- Resource / Delegate Permission Audit: Checking whether delegated user permissions or secondary shared calendar rights are causing orphaned synchronization loops.
Typical Effort Range
- Minor (2–5 Minutes): Deleting the event directly at
calendar.google.com, emptying the calendar Trash, and toggling offline settings. - Moderate (10–15 Minutes): Identifying and revoking faulty third-party CalDAV tokens or clearing app caches on mobile devices.
Related System Escalators
- If your calendar web view fails to load or throws an internal error during deletion, see “Calendar could not be loaded” (Internal Error).
- If you are experiencing CalDAV synchronization errors on secondary desktop or mobile clients, see “Secondary Calendar” not syncing via CalDAV.
- If sync delays between your phone and desktop are causing deletion updates to lag, see How to Resolve Sync Delay between Desktop/Mobile.
- For a comprehensive protocol on resetting corrupted calendar sync pathways, see The Google Calendar “Clean Sync” Master Guide.
Workspace Assessment
Ghost events are almost always the result of a desynchronized feedback loop between Google’s cloud server and a local third-party client. By executing deletions directly on the primary Google Calendar web server, clearing the cloud Trash bin, and temporarily severing external sync tokens, you eliminate the source of the re-upload loop and permanently erase the stubborn entry.