Regarding the update of the "Delete Date" for interactions on the same day

Hello,

We are planning to change the "Delete Date" for past interactions in the production environment in bulk, and we are currently testing this in a lab environment.
The APIs used are as follows.
GET /api/v2/analytics/users/details/jobs/availability
POST /api/v2/recording/jobs/
PUT /api/v2/recording/jobs/{jobId}
GET /api/v2/recording/jobs/{jobId}
We operate GCCX in the Tokyo region, and the "dataAvailabilityDate" is updated daily around 8:00 PM (JST).
The date and time when the data lake can be updated is indicated to be until around 6:00 PM (JST).
{
"dataAvailabilityDate": "2024-12-17T09:10:05Z"
}
In this situation, I executed the API (/recording/jobs/), and the data for the day was updated when the API was run after 10:00 PM (JST). The data was not updated when the API was executed between 8:00 PM and 10:00 PM.
There are only two pieces of data to be updated, and I have also confirmed that they are "FULFILLED."
We repeated the same test for several days, but the results were the same.
Is it by Genesys's design that the "Delete Date" for interactions cannot be updated for about two hours after the "dataAvailabilityDate" is updated?

Best regards,
Hirofumi Enotani

@enotani
I don't see delete date in this schema in either conversation jobs or user jobs.

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