Stuck on a problem and need help troubleshooting a persistent timeout issue with our custom Data Action designed to push recording metadata to an S3 bucket for legal discovery. The environment is Genesys Cloud 2024-3 in the eu-west-2 region. The flow triggers a webhook to our intermediate Lambda function, which then writes the JSON payload to S3.
The problem is that for bulk exports exceeding 500 recordings, the Genesys Data Action consistently returns a 504 Gateway Timeout after exactly 30 seconds. The Lambda function itself completes in under 5 seconds, as verified in CloudWatch logs. It seems Genesys is not receiving the HTTP 200 response from our endpoint in time, or the payload size is causing a bottleneck in the outbound connection from the Genesys edge.
We have tried increasing the Lambda timeout to 15 minutes, but the Genesys side still fails. The error log in Genesys shows: DataActionExecutionFailed: Webhook request timed out waiting for response.
Context:
- The payload includes
recordingId,conversationId,startTime,endTime, andparticipantsfor each recording. - We are using the
POST /api/v2/analytics/conversations/recordings/queryendpoint to fetch the initial list, then iterating through IDs. - The S3 bucket is in
eu-west-2to minimize latency. - Chain of custody requires the metadata to be written atomically, so we cannot split the batch smaller than 500 without breaking our audit trail logic.
Is there a known limit on the payload size for Data Action webhooks? Or is there a recommended pattern for handling large batches of recording metadata exports without hitting this timeout? We need a reliable method to ensure all metadata is captured for the legal hold request without manual intervention.