Why does this setting in the bulk export configuration trigger a 403 Forbidden error when requesting WhatsApp interaction metadata? The job initiates successfully via the /api/v2/recordings/bulk-export endpoint, but the status changes to FAILED after approximately 30 seconds. The error payload indicates a permission mismatch specifically regarding the digital_channel_metadata field. This is occurring on a Genesys Cloud instance in the EU-West region, using the latest Python SDK for job submission.
We have verified that the service account possesses the Recording:Read and Digital Channel:Read permissions. Voice recording exports complete without issue, and the chain of custody metadata is present. However, any export request that includes the digital channel wrapper data fails at the ingestion phase. The audit trail shows no explicit access denial events, which makes troubleshooting difficult. We need to preserve the full interaction context for legal discovery requests, so filtering out the metadata is not a viable option. Is there a specific configuration flag or additional scope required for bulk jobs accessing digital channel payloads? The standard documentation does not mention a separate permission set for this combination of data types.