I am currently facing a challenge with the Genesys Cloud RecordingApi.
To provide some context, my system was working seamlessly with an S3 bucket integration and a policy, until the policy was inadvertently deleted for a period of approximately four days. Though the policy has since been reinstated, this incident led to a data gap for the said interval.
In an attempt to recover the missing data, I tried using the RecordingApi's EXPORT bulk action to create a RecordingJobsQuery. The job creation appears to be working, but the job processing is where the problem emerges, as the recordings are failing. Here is the output:
{
'entities': [
{
'date_created': datetime.datetime(2023, 6, 1, 18, 39, 8, 614000, tzinfo=tzutc()),
'error_message': None,
'failed_recordings': None,
'id': '---',
'percent_progress': 42,
'recording_jobs_query': {
'action': 'EXPORT',
'action_date': datetime.datetime(2023, 6, 1, 18, 49, 7, 654000, tzinfo=tzutc()),
'conversation_query': None,
'include_screen_recordings': True,
'integration_id': '---'
},
'self_uri': '/api/v2/recording/jobs/---',
'state': 'PROCESSING',
'total_conversations': 36087,
'total_failed_recordings': 23800,
'total_processed_recordings': 23800,
'total_recordings': 55647,
'total_skipped_recordings': 0,
'user': {
'id': '---',
'self_uri': '/api/v2/users/---'
}
}
],
'total': 1
}
As per the output, the state of the job is still "PROCESSING", and the "total_failed_recordings" match the "total_processed_recordings", implying that all processed recordings are failing. This continued all the way to 100%.
I was hoping that someone in this community might have encountered a similar issue and could provide some guidance on how to effectively recover the missing data via the RecordingApi or any other feasible methods.
Additionally, is there a way to get a more detailed error message or some form of log for these failures? This would be greatly beneficial in further understanding and troubleshooting the issue.