Outlook ‘Item Cannot Be Saved. Object Has Been Deleted’: Sync Conflict Fix

When you try to save or move an email, calendar appointment, or contact in Outlook, you see the error: “Item Cannot Be Saved. Object Has Been Deleted.” This error occurs because of a sync conflict between your local Outlook data file and the Exchange server or your IMAP/POP3 email provider. The item you are trying to edit no longer exists on the server, but a copy remains in your local cache. This article explains exactly what causes this sync conflict and provides step-by-step methods to resolve it, including clearing the conflict, recreating the item, and preventing it from happening again.

Why Outlook Shows the “Object Has Been Deleted” Error

The error occurs when Outlook tries to save changes to an item that the server has already deleted. This happens most often in shared mailboxes, public folders, or calendars where multiple users manage the same items. When User A deletes an appointment from a shared calendar, the server removes it. If User B still has a cached copy of that same appointment and tries to save a change, Outlook sends a save request to the server. The server responds that the object no longer exists, triggering the error.

The same conflict can happen with your own mailbox if your local cache is out of sync with the server. For example, if you delete an email using Outlook on the web or your mobile device, but your desktop Outlook still has a cached copy, editing that email in desktop Outlook will produce this error. The root cause is always a mismatch between the local cached copy and the server-side truth.

How Cached Exchange Mode Creates Conflicts

Cached Exchange Mode downloads a copy of your mailbox to an offline Outlook Data File (.ost). This allows fast access and offline work. However, when changes are made on the server by another device or user, the local .ost file does not update instantly. If you edit an item that the server no longer has, Outlook tries to sync the change and fails, producing the error message.

Step-by-Step Methods to Fix the Sync Conflict

Use these methods in order. The first method resolves most cases. Move to the next method only if the error persists.

Method 1: Delete the Cached Conflict Copy

1. Locate the item in your current folder
   Open the folder that contains the item showing the error. This is usually Inbox, Calendar, or Contacts. Look for the item that triggers the error when you try to save it.
2. Delete the item from Outlook
   Right-click the item and select Delete. If the item is a recurring appointment, choose Delete this occurrence or Delete the series. Confirm the deletion when prompted. This removes the orphaned cached copy from your local .ost file.
3. Empty the Deleted Items folder
   Go to the Deleted Items folder, right-click it, and select Empty Folder. This ensures the orphaned record is fully purged from your local cache and cannot trigger the error again.
4. Recreate the item from server data if needed
   Open the shared mailbox, public folder, or your own mailbox using Outlook on the web. Locate the original item if it still exists on the server. If the item is truly gone, you must create a new one. For example, create a new calendar appointment with the same details.

Method 2: Switch to Online Mode to Force Server Sync

1. Open Outlook account settings
   Go to File > Account Settings > Account Settings. Select your email account and click Change.
2. Disable Cached Exchange Mode
   Uncheck the box labeled Use Cached Exchange Mode. Click Next, then Finish. Outlook will restart and connect directly to the server in online mode.
3. Edit or delete the conflicting item
   Open the folder that contains the item. In online mode, Outlook shows only the server-side data. If the item still appears, delete it. If it does not appear, the conflict is resolved.
4. Re-enable Cached Exchange Mode
   Go back to File > Account Settings > Account Settings, select your account, and click Change. Check Use Cached Exchange Mode, click Next, then Finish. Outlook restarts and downloads a fresh server copy to your .ost file.

Method 3: Repair the Outlook Data File

1. Close Outlook
   Make sure Outlook is not running. The repair tool cannot access the file while Outlook is open.
2. Locate the Scanpst.exe tool
   In Windows 11 or Windows 10, the tool is at C:\Program Files\Microsoft Office\root\Office16\SCANPST.EXE for Microsoft 365. For Outlook 2021 or 2019, the path may be C:\Program Files\Microsoft Office\Office16\SCANPST.EXE.
3. Run the Inbox Repair Tool
   Open Scanpst.exe. Click Browse and navigate to your .ost file. The default location is C:\Users\[YourUsername]\AppData\Local\Microsoft\Outlook. Select the .ost file and click Start. The tool scans and repairs corruption that may cause sync conflicts.
4. Restart Outlook and test
   Open Outlook. Try to edit or save the item that previously showed the error. If the error is gone, the repair resolved the conflict.

If Outlook Still Shows the Error After the Main Fix

Error appears on a recurring meeting series

Recurring meetings in shared calendars are especially prone to this error. One attendee may delete their instance, but other attendees still have the cached series. To fix this, open the recurring meeting in Outlook on the web. Change the recurrence pattern to No End Date and save. Then change it back to the original pattern and save. This forces the server to regenerate the series and syncs fresh copies to all attendees. If the error persists, delete the entire series from the shared calendar and recreate it.

Error occurs when moving an email to a different folder

If you get the error while dragging an email to another folder, the email was already moved or deleted on the server by another device. Open the source folder in Outlook on the web. If the email is there, move it to the target folder from the web interface. If the email is gone from both locations, it was permanently deleted. Recover it from the Recoverable Items folder in Exchange admin center if needed, or accept that the email is lost and continue.

Error appears every time you open a specific folder

This indicates a corrupted view or a stuck sync conflict on the folder itself. Create a new Outlook profile to test. Go to Control Panel > Mail > Show Profiles > Add. Name the profile and configure your email account. Open Outlook with the new profile. If the error is gone, the original profile had a corrupted folder view. Delete the old profile and continue using the new one.

Cached Exchange Mode vs Online Mode: Key Differences

Item	Cached Exchange Mode	Online Mode
Description	Downloads a local copy of mailbox to .ost file for fast access and offline work	Connects directly to Exchange server with no local cache
Sync frequency	Syncs every few minutes or on demand; can cause delays	Real-time sync; changes appear immediately
Offline access	Full offline access to cached items	No offline access; requires server connection
Conflict risk	Higher risk of sync conflicts like the Object Has Been Deleted error	Lower risk; no local cache to become stale
Performance	Faster for large mailboxes with slow connections	Slower for large mailboxes on slow networks

The error “Item Cannot Be Saved. Object Has Been Deleted” is a sync conflict caused by a stale local cache. Deleting the cached copy, switching to online mode, or repairing the data file will resolve it. To prevent future conflicts, avoid editing items in shared folders immediately after another user makes changes. Wait for the sync to complete, or use Outlook on the web for shared folder edits. If the error recurs frequently, consider running Outlook in online mode for shared mailboxes by disabling Cached Exchange Mode for that account only.