Recurring "Something went wrong" Calendar Event Creation Error

Question

Environment:

• OS: Windows

Clients Affected: Microsoft Teams, Teams Web App, and Outlook Web

Account Type: Office 365 / Exchange Online

Issue Description: I am repeatedly unable to create new calendar events or meetings. When attempting to save an event, I receive a popup error stating: "Something went wrong. We couldn't send your calendar event. Waiting a bit might help. Keep your calendar event open to try again later." Signing out and signing back into the application temporarily resolves the issue, but the error consistently returns after a short period.

Could you please help identify what is causing this bug and provide the appropriate solutions to resolve it?

Answer 1

Dear @Osman Ergun,

I hope you’re having a good day.

Thank you for taking the time to provide such a detailed description of the issue and the troubleshooting you've already performed.

Based on the symptoms you've described, the behavior appears to match a service incident that Microsoft has previously identified and investigated. Specifically, affected users were intermittently unable to create or save calendar events that included Microsoft Teams meetings when using Outlook on the web or the new Outlook for Windows, often receiving an error similar to:

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

Microsoft's investigation determined that this issue was caused by a service-side code regression in Exchange Online introduced during a framework upgrade. Under certain conditions, calendar events that contained linked online meetings (such as Teams meetings) could fail to process correctly, preventing users from saving or creating those meetings. Engineering teams collected diagnostic traces, identified the root cause, developed a targeted fix, and deployed the correction across affected environments. According to the incident summary, the issue has since been mitigated and the advisory has been closed.

For reference, other customers have reported very similar symptoms in Microsoft Q&A: User Unable to create Teams meetings - Microsoft Q&A

Given the similarities, I wanted to share this information in case it helps explain the behavior you're seeing.

---

Based on the information available, if the issue is still occurring in your environment despite the advisory being closed, I would recommend raising a support ticket with Microsoft. This will allow the support team to review tenant-specific diagnostics, collect logs if necessary, and determine whether the behavior is related to the previously identified incident or a separate issue affecting your environment.

If you are not the Microsoft 365 administrator for your organization, please contact your IT administrator and ask them to:

• Review the Microsoft 365 Service Health dashboard for any related advisories or incidents.
• Open a support request with Microsoft on your behalf if the issue persists. You can raise support ticket from Microsoft 365 Admin Center>Support>Help & Support.   For reference:  Get support | Microsoft Docs   
  • Provide the support team with details about the affected user(s), error message, and troubleshooting already performed to help expedite the investigation.

Since support engineers have access to backend diagnostic tools and tenant-level information that are not available through the community forum, they will be in the best position to perform a deeper investigation and identify the root cause if the problem continues.

I hope this information helps. Thank you again for taking the time to share the details of your experience with the community, and I wish you all the best in getting the issue fully resolved.

Warm regards.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

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.