Recordings Bulk Export

I've written a bulk export app that writes recordings to an S3 bucket, following this article:

I ran it on a test AWS instance and it worked fine; the recordings appeared in the S3 bucket.

I set up the integration on test and it activated successfully, creating a text file in the S3 bucket to prove it has access. However, when I run the app with the live details, the recordings are not written despite the app not erroring and giving the following messages

ClientID: xxxxxxxxxxxxxxxxxxxxx
crabulkexport/BulkExport.js:30
Client Secret: xxxxxxxxxxxxxxxxxxxxx
crabulkexport/BulkExport.js:31
Region: eu_west_2
crabulkexport/BulkExport.js:32
IntegrationID: 66dbe589-fd3e-4da3-ba41-ea635b11b3a4
crabulkexport/BulkExport.js:33
euw2.pure.cloud
crabulkexport/BulkExport.js:39
Running export with interval 2022-12-21T00:00:00.000Z/2022-12-21T23:59:59.000Z
crabulkexport/BulkExport.js:171
Successfully created recording bulk job
crabulkexport/BulkExport.js:83
9
State is PENDING.
crabulkexport/BulkExport.js:193
State is READY.
crabulkexport/BulkExport.js:193
Job is now ready: 7633222e-28ab-48da-9a7c-7366fe5de514
crabulkexport/BulkExport.js:90
Successfully executed recording bulk job
crabulkexport/BulkExport.js:95
{entities: Array(2), pageSize: 25, pageNumber: 1, total: 2, firstUri: '/api/v2/recording/jobs?pageSize=25&pageNumbe…ANCELLED&jobType=EXPORT&showOnlyMyJobs=true', …}
Successfully cancelled recording bulk job
crabulkexport/BulkExport.js:100
Successfully get recording bulk jobs

I've checked all permissions, but they all seem fine. Is there any logging/tracing in Genesys that I could turn on to see what's going on?

The getRecordingJobs response shows that we have 8 failed recordings.

totalConversations: 13
totalFailedRecordings: 8
totalProcessedRecordings: 8
totalRecordings: 8
totalSkippedRecordings: 0

But no idea why it's failing. The Integration has the correct permissions.

Hi @nick.wright
You can try getting more details about the job using this endpoint: GET /api/v2/recording/jobs/{jobId}
It will give you the status of the job, an errorMessage field describing any error that occurred during execution, and recordingJobsQuery containing the query that begat the job

1 Like

thanks, I'll try that

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.