Hello!
We have been using /api/v2/recording/batchrequests to download our recordings for the last few years, but since Monday we are not able to finish this task. It has usually taken around 1 hour to complete, sometimes a little bit more, but now it has ran for over 12 hours without finishing.
I did some test yesterday and it seems like regardless of the amount of parallelisation or the size of each batchrequest, only about half finishes and then it stops processing the rest of the batchrequest.
I do calls to /api/v2/recording/batchrequest/(jobid) to check the progress and ResultCount is stuck at the same value it is at from bascially a few minutes into the run.
I have also checked /api/v2/recording/jobs to see if any batchjobs are running but it seems like that is not the endpoint for that so I cant really see what is going on.
LIke I said, we have been using this solution for years before this and it suddenly stopped working. Did something change over the weekend that I'm not aware of?
Regards Daniel