Having some issues getting my configuration to work as expected for a specific batch of digital channel recordings that require strict chain of custody verification. We are running a bulk export job via the /api/v2/recording/bulkexports endpoint to retrieve WhatsApp and SMS interactions from the last fiscal quarter for a legal discovery request. The job ID is REC-BULK-EXP-9921-XJ. The status has remained stuck in QUEUED for over 48 hours, which is highly unusual given our typical throughput of 10,000 interactions per hour. The environment is Genesys Cloud EU (euw2), and we are using the standard OAuth 2.0 service account with the Recording:Read and BulkExport:Read permissions. The request payload specifies the filter for digital channels only, excluding voice calls to reduce load. However, when checking the job details via GET /api/v2/recording/bulkexports/{bulkExportId}, the response indicates no errors but provides no progress metrics. The metadata for these specific interactions includes sensitive PII that triggers our internal legal hold policies. We suspect the issue might be related to the size of the metadata payload or a timeout in the S3 integration layer, as our bucket is in us-east-1 while the tenant is in eu-west-1. We have verified that the S3 bucket policy allows cross-region writes and that the IAM role attached to the service account has s3:PutObject permissions. No 403 or 500 errors are logged in the platform audit trail. The previous exports for voice channels completed successfully in under 2 hours. We need to understand if there is a known limitation with digital channel metadata extraction in bulk exports or if we need to adjust the pagination settings in the API request. Any insights on why the job remains in QUEUED without failure logs would be appreciated, as this delay impacts our legal discovery timeline.