Topic
Task notifications will intermittently stopped working. The following errors can be seen in the HostServer logs:
SourceCode.Workflow.Shapes.Execution.Mail.EWS: Exchange error code: ErrorServerBusy Exchange error: Microsoft.Exchange.WebServices.Data.ServerBusyException: The server cannot service this request right now. Try again later.at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ProcessWebException(WebException webException)at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalCreateItems(IEnumerable`1 items, FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode, ServiceErrorHandling errorHandling)at Microsoft.Exchange.WebServices.Data.Item.InternalCreate(FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode)at.
"Error","General","0","ErrorMessage","SourceCode.Workflow.Common.EWS: ","0 The Exchange server is busy. Attempting to retry."
Instructions
The "Exchange Server is busy" error is generated by Exchange when a usage limit has been exceeded.
Exchange Online enforces various service limits, which are documented here:
https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits
To identify the specific limit that was triggered, review your Exchange logs. Most limits are temporary and will reset automatically after a certain period. The duration depends on the specific limit exceeded.
Unfortunately this behavior is controlled by Exchange. K2 cannot bypass or override these limits. If you encounter this error frequently, consider optimizing your workflows to reduce the volume of emails sent by K2.