So I’m seeing a very odd bug with our bulk export pipeline for legal discovery requests involving digital channels. We are using a Bring Your Own Cloud setup with AWS S3, specifically leveraging the Edge Gateway for data residency compliance. The issue manifests when exporting WhatsApp interactions that have been tagged with a legal hold flag. The initial export job initiates successfully via the POST /api/v2/bulkexport/jobs endpoint, returning a 201 Created status with a valid job ID. However, approximately 40% through the processing phase, the job status flips to ‘FAILED’ with a generic error code EXPORT_JOB_TIMEOUT. Checking the detailed logs via GET /api/v2/bulkexport/jobs/{id}/details reveals a specific failure message: ‘Edge connection terminated unexpectedly during chunk transfer.’ This is particularly confusing because our network connectivity to the S3 bucket is stable, and we have verified the IAM roles attached to the Edge Gateway have full s3:PutObject permissions. We suspect this might be related to the payload size of the digital channel metadata, which includes extensive JSON blobs for message history. Interestingly, voice recordings from SIP trunks export without issue, suggesting the problem is isolated to the digital channel data structure or the way the Edge Gateway handles large JSON payloads versus binary audio streams. We are running Genesys Cloud version 2024.1.0 and using the latest version of the Edge Gateway software. The environment is deployed in the eu-west-2 region. We need to ensure chain of custody integrity, so we cannot simply retry without understanding the root cause, as inconsistent exports could jeopardize the legal discovery process. Has anyone experienced similar timeout issues with large digital channel exports through the BYOC Edge Gateway? We are considering splitting the export by date ranges to reduce payload size, but we want to confirm if this is a known limitation or a configuration error on our end before proceeding with workarounds.