The data action upload-to-s3 is failing with a GatewayTimeout (504) when processing the final batch of a bulk export job for WhatsApp transcripts. The export was initiated via POST /api/v2/analytics/conversations/details/query with the correct application/json content type and valid OAuth2 token. The environment is Genesys Cloud EU-West-1. The S3 bucket policy allows PUT requests from the Genesys Cloud IP range, and test uploads from other sources succeed without issue. The failure occurs specifically when the payload size exceeds 50MB, which suggests a potential issue with chunked transfer encoding or the S3 multipart upload configuration within the data action. The error log shows: Error: Request timed out after 30000ms. We have verified that the IAM role attached to the S3 bucket has s3:PutObject and s3:AbortMultipartUpload permissions. The chain of custody requirement mandates that all metadata, including message direction and timestamp, must be preserved in the exported JSON file. Has anyone encountered a similar timeout issue with large digital channel exports? We are considering breaking the export into smaller date ranges, but this complicates the legal hold process. Any insights on the optimal payload size for S3 data actions would be appreciated.