What is the standard approach to handle S3 upload timeouts when exporting large batches of digital channel recordings for legal discovery?
We are using Genesys Cloud v2024.07 in the EMEA region. The process involves triggering a bulk export job via the /api/v2/bulkexport/jobs endpoint, filtering for interactions tagged with ‘legal_hold_active’. These jobs are configured to push data to an external S3 bucket using the standard Data Actions integration.
Recently, jobs containing more than 5000 WhatsApp transcripts fail with a 504 Gateway Timeout error from the S3 endpoint, even though the bucket permissions are verified and the network path is stable. The bulk export job status remains ‘IN_PROGRESS’ indefinitely until it eventually fails with ‘EXPORT_FAILED’. The audit trail shows the data was successfully queried from Genesys, but the transfer to S3 never completes.
Is there a specific payload size limit or timeout configuration for the S3 Data Action that we are missing? We need to ensure chain of custody is maintained without data loss. Any insights on adjusting the chunk size or retry logic for these integrations would be appreciated.
Thanks for the help.