Errors in email log

[JJ]

In the email log for my Service Desk project, I see this error message sporadically in the logs: "com.microsoft.graph.core.ClientException: Error during http request."  Email seems to be received without any issue into the Service Desk system, but this error continues.  Interestingly, it is typically 1 minute after a successful log entry.

[Kathy Burton]

We are seeing the same thing. And intermittent emails being accepted and creating tickets.

[Beau Johnson]

From my recent ticket to Atlassian on this:

------

This error may occur due to any glitches during the connection time with Microsoft Servers, but it should not affect your mail processing. Allow me to share with you that Jira tries to pull messages from your mail server every minute, so even though it fails we will very likely connect on the next try.

Besides that, allow me to share with you a bug that they had on Microsoft Graphs and their comment when the ticket was closed:

https://github.com/microsoftgraph/msgraph-sdk-java/issues/162

...
At this time the API I added is not optimal (you've probably noticed that it requires passing the authentication provider multiple time), this is something we'll clean up whenever we replace the current authentication stack by azure-identity.

With that said, allow me to share with you an excerpt from our logs while those errors are happening.

stack: java.io.IOException: com.microsoft.graph.core.ClientException: Error during http request        at...Could not retrieve access token for connection     

So, once they are able to clean that up, this should reflect on the Jira end as well.

------

Hope this helps!

[Stanislav Vincent]

We are facing the same issue and found out that even we do have set that anyone can create the ticket only some will go through and are registered at the end as new tickets. Any help would be appreciated. Thanks

[Steven Lean]

Hi mate, was facing same thing. any progress on this error?

[Beau Johnson]

I posted an answer from a recent ticket, but it seems it was taken down. My suggestion, make a ticket with Atlassian for the answer.