Legacy Dev Forum Posts

fridden40 | 2022-07-14 11:39:47 UTC | #1

Hi Everyone,

I have an AWS S3 bucket integration in my organization. I have a policy that exports the recordings of several queues to the Bucket and it´s working fine, since I created the policy. So with this I´m pretty sure that the integration with the Bucket works.

Also, I needed to export recordings from these same queues to the bucket, but in a time range before the policy was created. To achive this, I have run requests to the API from the API Explorer, in the developer tools page. The requests that I executed were these:

1. POST /api/v2/recording/jobs

body: { "action": "EXPORT", "actionDate": "2022-07-14T12:00:00.000Z", "integrationId": "d01db3e5-7b30-48f9-8c76-5cf8265f58a0", "includeScreenRecordings": false, "conversationQuery": { "interval": "2021-12-30T00:00:00.000Z/2021-12-31T00:00:00.000Z", "segmentFilters": [ { "type": "and", "clauses": [ { "type": "or", "predicates": [ { "type": "dimension", "dimension": "queueId", "value": "e1c0004c-4eaa-4baa-adeb-6aa8bab22d05" },

...

] } ] } ] } }

Whit this request I created the job successfully, and after the State of the Job changes to READY it shows that I have 83 converstations and 74 recordings. So, the query retrieves results.

Then I change the state of the job to PROCESSING with this request:

2. PUT /api/v2/recording/jobs/980226e3-1d8c-4c5b-8bf5-02deca8e5408

body: { "state": "PROCESSING" }

3. I checked the state of the job until the state was FULFILLED and this was the result:

{ "id": "980226e3-1d8c-4c5b-8bf5-02deca8e5408", "state": "FULFILLED", "recordingJobsQuery": { "action": "EXPORT", "actionDate": "2022-07-14T10:00:00Z", "integrationId": "d01db3e5-7b30-48f9-8c76-5cf8265f58a0", "includeScreenRecordings": false, "conversationQuery": { … }, "dateCreated": "2022-07-14T08:54:17.751Z", "totalConversations": 83, "totalRecordings": 74, "totalSkippedRecordings": 0, "totalFailedRecordings": 74, "totalProcessedRecordings": 74, "percentProgress": 100, "failedRecordings": "/api/v2/recording/jobs/980226e3-1d8c-4c5b-8bf5-02deca8e5408/failedrecordings", "selfUri": "/api/v2/recording/jobs/980226e3-1d8c-4c5b-8bf5-02deca8e5408", "user": { "id": "08938ccc-d225-4800-9b22-8e8b8fdaef5d", "selfUri": "/api/v2/users/08938ccc-d225-4800-9b22-8e8b8fdaef5d" } }

The point is:

• My user has Master Admin role, so in theory I was able to execute this job properly.
• The S3 integration is working fine, because I have a policy that exports current recordings in these queues and it´s working fine.
• The query retrieves some valid conversations and recordings, and I was able in the Genesys Cloud Agent Interface to listen and download these recordings with my user, so I have permissions in the recordings, and the recordings exits.
• I have checked the recordings in this request:

GET /api/v2/recording/jobs/980226e3-1d8c-4c5b-8bf5-02deca8e5408/failedrecordings

and then checked the results in this other request:

GET /api/v2/conversations/61ddf736-8a5a-4d7b-b780-c4300fbccffe/recordings/0269dcb2-597a-4b91-b57b-44eb7365db80

I could retrieve the recording and in the API response there is no trace of ExportDate, ExportedDate or DeletedDate fields, so these recordings were no exported before.

With all these things. Why all the recordings failed from the export? I was doing something wrong?

Regards,

David García García Developer at Telefonica, Spain

Eos_Rios | 2022-07-14 12:18:52 UTC | #2

Nothing jumps out at me but even with all that detail you need to open a customer care case so the direct customer support can examine your specific scenario in even more detail to determine what's going on behind the scenes since the support here can't do that.

John_Carnell | 2022-07-26 16:00:39 UTC | #3

This post was migrated from the old Developer Forum.

ref: 15510