We have a JIRA Cloud backup that keeps throwing an error on the AuditRecords part of the backup. This is the error message that's displayed:
{ "errorMessages": [ "Internal server error" ], "errors": {} }
There's no other information available as far as I can tell, so we have nothing to go on in terms of investigating the problem. Any thoughts?
Hi Graham,
Thank you for submitting a ticket with us.
Let's check if the error will be reproduced with an export package.
Please click Integration on the left pane in your account, right above the Backup, and create an export package by following this guide.
Select only AuditRecords object and run the package.
Let us know if the error appears again.
We are looking forward to hearing from you.
The export package failed in 43 seconds with a similar error message:
0 record(s)
AuditRecords ({ "errorMessages": [ "Internal server error" ], "errors": {} })
Hello Graham,
Thank you for getting back to us.
Please authorize us a test run on this export package.
We will not access any sensitive data. The package will be run with extended logging.
We are looking forward to your reply.
Yes, you have my authorization to do a test run on the export package. Anything I need to do in the application to allow that or is this message enough?
Dear Graham,
Thank you confirmation.
Your message is enough. We raised a ticket with our development team to investigate your case.
Once there are any details, we will update the post.
Dear Graham,
Our development team looked into your case.
During the process of reading AuditRecords, Skyvia reaches the next page and executes this request:
GET https://zenqms.atlassian.net/rest/api/3/auditing/record?limit=100&offset=900
It results in an error and Jira server sends us this response:
{"errorMessages":["Internal server error"],"errors":{}}
We tried to change a PageSize metadata parameter to 1000, as it is stated in Jira API documentation, and that didn't help. Before this change, a request failed when reading the page after a nine hundredth record. After the change it fails right away when reading the very first page, since there are 1000 records on one page.
Please reach out to Jira support and pass them our findings. They might be able to check out the reason of such server response.
We are looking forward to hearing from you.
