What is the standard approach to handle missing interaction IDs when exporting bulk recording data for legal discovery requests?
We are pulling chat transcripts and associated audio from the Digital Channels API for a specific case. The export job completes successfully, but the CSV manifest contains null values for the interactionId field on approximately 15% of the records. This breaks our chain of custody verification script, which relies on matching the transcript ID to the audio file hash.
The environment is Genesys Cloud EU-West. We are using the Python SDK v2.18.0. The service account has recording:export and digital:read permissions. We verified that the interactions exist in the UI and have valid IDs there.
The error log from our validation script shows:
{
"status": "error",
"message": "Missing required field: interactionId",
"record_count": 142
}
Is this a known limitation with the bulk export API for digital channels? Or is there a specific filter parameter we need to include in the POST request to ensure metadata completeness? We need a reliable way to link these records before the court deadline.