Struggling to figure out why the Create Recording Export Job data action consistently fails when attempting to map the media_url field from WhatsApp interactions to the S3 destination bucket. The Architect flow is configured to trigger on Interaction Created for digital channels, but the execution log shows a 400 Bad Request with the message Field 'media_url' is not available for export in this context. The environment is Genesys Cloud EU, using the Python 3.9 SDK version 1.2.4 to initiate the bulk export. The S3 integration is verified and working for voice recordings, but digital channel metadata seems restricted. Is there a specific permission scope missing on the API user, or is the media_url field simply not supported in the data action schema for WhatsApp? The legal hold requirement mandates immediate preservation of the original media blob, not just the transcript. Any insight into the correct field mapping or a workaround to ensure the chain of custody remains intact would be appreciated. The job ID is exp-job-12345 and the error timestamp is 2023-10-27T14:30:00Z.