Genesys Cloud - Developer Community!

Hi everyone,

I am planning to use the /api/v2/recording/jobs API to bulk-archive recordings for a client.

I've been looking through the documentation but haven't found a recommended limit or best practice regarding the maximum size/volume a single job should handle.

For context, the client generates roughly 300GB of recordings per month.

• Is it feasible to process an entire month (300GB) in a single bulk job?

• Are the job limits constrained by total data size (GB), or is there a hard limit on the number of recording/conversation IDs passed per job?

If a single month is too large, what is the recommended batch size per job?

Thanks in advance!

Hi @Chanin Srisathian, hope you are doing fine.

From my experience, theres no recommended limit for a recording bulk export. What I've experienced is that some problems may occur with recordings when the export takes too long to complete (it could be related to the quantity of recordings or even the total size) as the download URL may expire after sometime (if the export hadnt ended, errors or broken files may appear).

What I did as "best practice" is to limit the number of recordings exported each time (from previous research around the Community, that I adopted myself, people do it around 100), with this you try to minimize the chance of the downloading URL to expire and blank/bugged files to appear.

Hope to have been able to help you in some way!

------------------------------
Diego Halter
------------------------------

Hi Diego,

Thanks for the reply!

You mentioned recording bulk exports and URLs expiring if the process takes too long. Do you happen to know if these same issues or performance bottlenecks occur when archiving recordings?

I am specifically using the /api/v2/recording/jobs endpoint with the archive action, so I'm wondering if the same size limits and risk of errors may apply to that process as well.