Looking for advice on a specific conflict error we are hitting when trying to export digital channel recordings for legal discovery.
Context:
Our environment uses Genesys Cloud with BYOC Edge. We are running a bulk export job for WhatsApp and Web Chat transcripts to meet a strict chain of custody requirement. The export is triggered via the Recording API. Voice recordings export without issue. However, when the job attempts to process digital channels routed via Predictive Routing, we get a 409 Conflict error in the job status endpoint.
The error message states: Resource conflict: Recording metadata locked by active routing session. This is strange because the calls are completed. We are using Architect flow version 2.4.1. The metadata seems to remain locked in the predictive routing queue even after the session ends, preventing the bulk export service from acquiring the necessary read locks for the S3 presigned URL generation.
Question:
Is there a known delay between the Predictive Routing session closure and the metadata release for digital channels? We need to ensure the audit trail is complete. Should we implement a retry logic with a specific backoff, or is there a configuration in the Architect flow that forces an immediate metadata release upon session termination?