JonasJonsson | 2024-03-05 09:20:46 UTC | #1
After performing changes in policys to retain recordings for a shorter time, we want use /api/v2/recording/jobs endpoint to change deletion date for all existing recordings so they are deleted according to the new rules, after 180 days.
We created the following job to try for a shorter timeperiod POST /api/v2/recording/jobs HTTP/1.1 { "action": "DELETE", "actionAge": 180, "conversationQuery": { "interval": "2023-06-01T00:00:00/2023-07-01T00:00:00" } }
Job is created, we execute it and it reaches status FULFILLED. However when we check we still see conversations within that interval that has recordings left and their deletion date is not changed.
Are we missing anything with the request?
SimonBrown | 2024-03-05 15:42:30 UTC | #2
Deletion is not instant. it is scheduled in the background and can take24hrs + to actually complete.
I would keep checking periodically, otherwise a support ticket.
JonasJonsson | 2024-03-06 07:23:22 UTC | #3
As I understand it, from reading other threads, the job only sets the deletion date and then actually deletion can take some time for background tasks to complete. In this case not even the deletion date is updated.
When checking the details of the executed job it shows "totalConversations": 1 even tough a lot of conversations fit in that interval. So the issue seems to be in that he conversationQuery does not match conversations as it should. I should also mention that in this org we have the setting "Maximum Interaction Data Retention Time" set to 180 days. So most data for these conversations has already been cleared, might be related.
I'd love to hear input from a Genesys Employee, mostly to say if we are using the API in a incorrect way or if there might be an underlying problem here. Perhaps @tim.smith could have a look?
tim.smith | 2024-03-06 13:52:00 UTC | #4
JonasJonsson, post:3, topic:25009
So the issue seems to be in that he conversationQuery does not match conversations as it should.
Please open a case with Genesys Cloud Care to investigate this issue. We do not have access to your org's data via the forum to verify the validity of any results from the API.
JonasJonsson | 2024-03-06 14:53:42 UTC | #5
Case is already opened.
But you don't see any direct issues with the request body when creating the job?
tim.smith | 2024-03-06 14:59:46 UTC | #6
I inferred that the request was successful from your first post, so the request is valid. If it weren't valid, you would receive an error and the job would not be created.
JonasJonsson | 2024-03-07 07:07:08 UTC | #7
OK, thanks. Let's see what Care can come up with.
system | 2024-04-06 07:08:06 UTC | #8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 25009