Hello,
We’ve identified an issue in Exalate for Jira Cloud that needs to be resolved as soon as possible.
Occasionally, the connection between Exalate and Jira Cloud is interrupted (“Connection reset” or “Read timeout”) or the Jira server returns a temporary server error (HTTP 500). When this happens, Exalate stops synchronizing the work item and waits for a manual “Resolve.” Clicking “Resolve” retries the synchronization, which then completes successfully.
This is problematic because it prevents some JSM requests from reaching the agents until the error is detected and resolved manually. We need an automatic retry feature implemented in Exalate for these types of errors.
Thanks.
There is an automatic retry in the product for many different cases. Probably this is one which has not been considered yet (although network problems are being retried, so strange)
Can you raise a support ticket if not done yet?
Hi Francis,
Nice to talk to you. I’ve already created a ticket to fix these errors, and the support team gave me a workaround to periodically fix the errors with Scriptrunner. However, it’s not the best solution. It was in that ticket that they also asked me to create this feature request.
It is a strange case because these errors began to occur without any changes being made and only happen on one of the connections that we have, although it is the most active one.