Share via

Teams Meeting Creation Failing Across All Clients and Devices - Error: "We couldn't save your calendar event"

Ricardo Zuleta 0 Reputation points
2026-05-26T20:02:09.5733333+00:00

Hi everyone,

I am troubleshooting an issue where a user is completely unable to create Teams meetings. The event simply fails to generate, and the behavior has isolated the issue strictly to the Microsoft backend.

The exact error message received on desktop/web is:

"Something went wrong. We couldn't save your calendar event. Waiting a bit might help. Keep your calendar event open to try again later. Resume editing"

Here is what we have verified and tested so far:

Cross-Platform Failure: The issue persists across Teams Desktop client, Outlook Desktop, Outlook Web App (OWA), and Teams Web.

Mobile Test (Crucial): We also tried scheduling the meeting using the Teams mobile app on a smartphone. No error messages are shown on the phone, but the event is not created either (it never syncs or sends the invite).

Environment/Client Cleared: Since it fails on an isolated mobile device and on web browsers, client-side caching, local OS corruptions, or Virtual Desktops have been completely ruled out.

The user's Exchange mailbox appears correctly provisioned. This strongly points to a Teams backend provisioning glitch or a corrupted tenant policy synchronization issue rather than a client-side problem.

Has anyone experienced this specific server-side handshake failure where even mobile scheduling is blocked? Any specific Get-CsOnlineUser parameters or switches we should look for to force a backend refresh?

Thanks in advance!

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Schedule meetings
0 comments No comments

1 answer

Sort by: Most helpful
  1. Kai-L 13,880 Reputation points Microsoft External Staff Moderator
    2026-05-26T21:51:13.1+00:00

    Dear @Ricardo Zuleta,

    Good day, and I appreciate the detailed description of your issue. As a forum moderator, I genuinely wish I could directly access your account or delve into the backend systems to investigate and fix this for you. However, our role here is limited to providing general guidance and solutions that can be applied by users. 

    From my research, the error message "We couldn't save your calendar event" when creating Teams meetings (failing across desktop, web, and mobile) usually indicates a problem with the user's Exchange mailbox provisioning or backend sync. Please try the following approaches and see if they help resolve the issue:

    1/ Create a new calendar and migrate items

    This is often the quickest way to restore normal editing functionality.

    In Teams, go to Calendar

    Select Add calendar > Create new blank calendar, then give it a name (for example, “Team Calendar New”)

    Move events from the affected calendar:

    • Open the impacted calendar
    • Right-click an event, select Duplicate event
    • Change the Calendar field to the new calendar, then save

    Repeat for other important events (you may prioritize upcoming events first)

    After confirming that events in the new calendar can be created and edited successfully, you may rename the old calendar (e.g., “Do not use”) and uncheck it.

    2/ Re-create or adjust your Outlook profile

    Sometimes this issue is related to profile configuration:

    • In New Outlook, go to File > Account Settings > Account Settings > Add Account, and add another mailbox (if available), then set it as the primary account temporarily
    • Alternatively, go to Control Panel > Mail (Microsoft Outlook) > Show Profiles, remove your current profile, and create a new one

    3/ Check for Mailbox Holds (In-Place or Litigation Hold) 

    If user account is on Litigation Hold or In-Place Hold, Outlook saves every version of an event in a hidden "Versions" folder. If this folder is full, you will be unable to save new changes or series. Please contact your IT Administrator to check if your mailbox has reached its Recoverable Items quota. They may need to temporarily adjust the hold or clear the Versions folder to allow new entries. If you don't know who your IT administrator is, please refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

    For reference: In-Place Hold and Litigation Hold in Exchange Server | Microsoft Learn

    4/ Run the Calendar checking tool (CalCheck) 

    This is an official Microsoft utility designed to detect and repair corrupted calendar items.

    1. Please download: Download Calendar Checking Tool for Outlook from Official Microsoft Download Center
    2. After installing, open the Command Prompt, type the following command, and press Enter: calcheck -f -r
    3. This will scan your calendar and attempt to repair problematic entries.

    5/ Contact Microsoft Support

    If the issue persists after these checks, ask your IT administrator to submit a support request directly to Microsoft Support team. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.

    I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this. Thank you for your patience and understanding. If you have any questions or need further assistance, please feel free to share them in the comments so I can continue to support you. I'm looking forward to your reply.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.