Genesys Cloud - Developer Community!

Hello,

Our organisation is using the AWS S3 Recording Bulk Actions Integration to export recordings from Genesys Cloud to an S3 bucket.

We've successfully configured the integration - test calls are appearing in the bucket when using Policies with the "Export copy of recordings" action. So we know the integration is working for live calls.

We understand that Policies do not apply retroactively, so to export historical interactions (e.g., calls handled in Aug-25), we're using the Recording Bulk Job API.

We submitted a job using /api/v2/recording/jobs with the following parameters:

• action: EXPORT
• actionDate: 2025-09-26T12:00:00Z
• integrationId: [redacted]
• segmentFilters: filtering by a specific userId and queueId
• interval: 2025-08-01 to 2025-08-31

The job was created successfully and returned the following status:

However, several hours later:

• The job is still in "READY" state.
• No recordings have been processed.
• No new files have appeared in the S3 bucket.

Question: Is there anything else I can do to troubleshoot this job or confirm whether it's stuck?
Are there known delays or conditions that might prevent the job from progressing?

Any guidance would be greatly appreciated!

Hello,

Our organisation is using the AWS S3 Recording Bulk Actions Integration to export recordings from Genesys Cloud to an S3 bucket.

We've successfully configured the integration - test calls are appearing in the bucket when using Policies with the "Export copy of recordings" action. So we know the integration is working for live calls.

We understand that Policies do not apply retroactively, so to export historical interactions (e.g., calls handled in Aug-25), we're using the Recording Bulk Job API.

We submitted a job using /api/v2/recording/jobs with the following parameters:

• action: EXPORT
• actionDate: 2025-09-26T12:00:00Z
• integrationId: [redacted]
• segmentFilters: filtering by a specific userId and queueId
• interval: 2025-08-01 to 2025-08-31

The job was created successfully and returned the following status:

However, several hours later:

• The job is still in "READY" state.
• No recordings have been processed.
• No new files have appeared in the S3 bucket.

Question: Is there anything else I can do to troubleshoot this job or confirm whether it's stuck?
Are there known delays or conditions that might prevent the job from progressing?

Any guidance would be greatly appreciated!

Hello,

I haven't used the recoding export to S3 for several years. But I remember that once the job is ready, you need to start its execution.

See this step: https://developer.genesys.cloud/analyticsdatamanagement/recording/recordings-bulk-action#execute-job

When the status of the job is READY, it means the job is ready to be executed

You can then request to execute the job (setting the job state to PROCESSING using PUT /api/v2/recording/jobs/{jobId})

Genesys Cloud will start processing the job (job state = PROCESSING). When it has finished completing the job, the job state should show as FULFILLED.

Regards,

Hello,

Our organisation is using the AWS S3 Recording Bulk Actions Integration to export recordings from Genesys Cloud to an S3 bucket.

We've successfully configured the integration - test calls are appearing in the bucket when using Policies with the "Export copy of recordings" action. So we know the integration is working for live calls.

We understand that Policies do not apply retroactively, so to export historical interactions (e.g., calls handled in Aug-25), we're using the Recording Bulk Job API.

We submitted a job using /api/v2/recording/jobs with the following parameters:

• action: EXPORT
• actionDate: 2025-09-26T12:00:00Z
• integrationId: [redacted]
• segmentFilters: filtering by a specific userId and queueId
• interval: 2025-08-01 to 2025-08-31

The job was created successfully and returned the following status:

However, several hours later:

• The job is still in "READY" state.
• No recordings have been processed.
• No new files have appeared in the S3 bucket.

Question: Is there anything else I can do to troubleshoot this job or confirm whether it's stuck?
Are there known delays or conditions that might prevent the job from progressing?

Any guidance would be greatly appreciated!

Hello,

I haven't used the recoding export to S3 for several years. But I remember that once the job is ready, you need to start its execution.

See this step: https://developer.genesys.cloud/analyticsdatamanagement/recording/recordings-bulk-action#execute-job

When the status of the job is READY, it means the job is ready to be executed

You can then request to execute the job (setting the job state to PROCESSING using PUT /api/v2/recording/jobs/{jobId})

Genesys Cloud will start processing the job (job state = PROCESSING). When it has finished completing the job, the job state should show as FULFILLED.

Regards,

Hello,

Our organisation is using the AWS S3 Recording Bulk Actions Integration to export recordings from Genesys Cloud to an S3 bucket.

We've successfully configured the integration - test calls are appearing in the bucket when using Policies with the "Export copy of recordings" action. So we know the integration is working for live calls.

We understand that Policies do not apply retroactively, so to export historical interactions (e.g., calls handled in Aug-25), we're using the Recording Bulk Job API.

We submitted a job using /api/v2/recording/jobs with the following parameters:

• action: EXPORT
• actionDate: 2025-09-26T12:00:00Z
• integrationId: [redacted]
• segmentFilters: filtering by a specific userId and queueId
• interval: 2025-08-01 to 2025-08-31

The job was created successfully and returned the following status:

However, several hours later:

• The job is still in "READY" state.
• No recordings have been processed.
• No new files have appeared in the S3 bucket.

Question: Is there anything else I can do to troubleshoot this job or confirm whether it's stuck?
Are there known delays or conditions that might prevent the job from progressing?

Any guidance would be greatly appreciated!