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:
{
"id": "a274fc6a-e32f-4597-8963-f6e8109de60c",
"state": "READY",
"totalConversations": 67,
"totalRecordings": 46,
"totalProcessedRecordings": 0,
"percentProgress": 0
}
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!
#API/Integrations#QualityManagement#Telephony#Unsure/Other------------------------------
Dan Wong
EUC Engineer
------------------------------