Problem:
using /api/v2/recording/jobs with action DELETE and metrics: ani and dnis would include recordings that are already marked for deletion but are not yet deleted by Genesys Cloud.
More detail:
we know that bulk delete may take some time be completed on Genesys side even after the delete job is marked as FULFILLED. The problem we are having is that the records that were set to be deleted in the previous job as still being included in the jobs that follow. In Genesys Workspace, under the interaction detail record under Recording it already has DELETE DATE set to today. Is there a way to filter the records that are already marked for deletion using either segment or conversation filters?