Does anyone understand why the data action in architect is timing out when trying to push bulk recording metadata to our s3 bucket for legal discovery requests
we are running a specific flow to export digital channel recordings (webchat and whatsapp) along with their associated metadata for a court order. the flow triggers a bulk export job via the recording api, which works fine. however, the subsequent data action that attempts to copy the resulting manifest file to our secure s3 bucket for chain of custody purposes is failing consistently.
the error returned in the architect flow logs is a 504 Gateway Timeout. this happens after the flow waits for the bulk export job status to change to ‘completed’. once complete, it calls the data action. the timeout occurs specifically during the http post request to the s3 put object endpoint. we have verified that the s3 bucket policy allows access from our genesys cloud ip ranges and the access keys are valid. we have also tested the endpoint externally with curl and it works instantly.
our environment is genesys cloud emea region, version 24.3. we are using the standard http client data action. the payload size is small, just a json manifest file under 1mb. we suspect this might be related to the way genesys handles outbound connections from the architect runtime or perhaps a latency issue with the emea region’s connection to aws eu-west-1.
we need to maintain strict audit trails for this data, so manual download is not an option. the flow needs to be automated. has anyone seen this specific 504 on data actions when integrating with s3 for bulk exports? is there a known limit on the http client timeout that we can adjust, or should we be using a different approach like a webhook instead? any help would be appreciated as we are under pressure to deliver these records.