We are experiencing a sudden interruption in service on the batch recording retrieval API resources. After creating a batch retrieval job at POST /api/v2/recording/batchrequests we then poll GET /api/v2/recording/batchrequests/{jobid} to find when the job has been completed. However, we have noticed that the jobs are frequently getting stuck at a result count that is less than the expected result count, and thus the batch retrieval job is never considered "complete." Can you please provide some guidance on what we can do to remedy this?
Please open a case with Care to investigate.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.