Hey everyone. I am absolutely loving the AWS EventBridge and Lambda integrations with Genesys Cloud. It makes serverless architecture so simple. I am currently building a Secure Flow to process credit card payments. I need to send the masked credit card token to our AWS Lambda function using a custom Data Action. The Data Action works perfectly in my standard inbound flows. But the moment I move it into the Secure Flow, the execution fails with a timeout error. I verified my IAM roles and everything is perfect on the AWS side. Are Data Actions restricted from making outbound HTTPS requests when executing inside a Secure Flow?
Good morning the previous poster. The timeout error you are experiencing is a known architectural protection mechanism. Secure Flows operate within a restricted memory space to ensure PCI compliance.
By default, Data Actions executed within a Secure Flow are explicitly prohibited from logging their request and response payloads. If your AWS Lambda function expects a specific payload format but the Secure Flow strips or encrypts the variables before transmission, the Lambda function will fail to process the request, resulting in a timeout on the Genesys Cloud side.
You must ensure that the variables you are passing to the Data Action are explicitly marked as ‘Secure’ within the Architect flow.
I encountered this identical issue while migrating a client from NICE CXone. CXone handles secure variables differently. In Genesys Cloud, if your Data Action attempts to write the secure variables to the execution logs, the Secure Flow will terminate the action.
You must verify that the Data Action configuration itself has the ‘Secure’ toggle enabled in the integration settings. If the Data Action is not flagged as secure at the integration level, the Secure Flow engine will block it from executing entirely.
I recently inherited this platform and ran into the exact same error. That is correct. It is not an AWS IAM issue.
You must navigate to the Integrations menu, open your specific AWS Lambda Data Action, and check the box labeled ‘Secure Data Action’. If this box is unchecked, Architect will automatically block the action from running inside any Secure Flow.
Once you enable that setting, the timeout will disappear and the Lambda function will trigger normally. Be aware that this also disables all troubleshooting logs for that specific Data Action across your entire organization.