Data Action Timeout on Large Payloads in Multi-Tenant App

Stuck on 504 Gateway Timeout errors when invoking a custom Data Action from Architect flows processing payloads exceeding 50KB.

The AppFoundry application is deployed across multiple tenant orgs using OAuth 2.0 client credentials flow. The Data Action endpoint is hosted on AWS API Gateway with a 30-second timeout, yet the Genesys Cloud platform consistently returns a 504 before the response is processed. This behavior is inconsistent; smaller payloads under 10KB return successfully with a 200 OK. The SDK version is purecloud-architecture-node 2.1.0. The integration logs show the request reaches the Lambda function, but the connection drops during the response phase. Is there a hidden payload size limit or a specific configuration in the Data Action definition that needs adjustment for larger data transfers?

As far as I remember, the platform imposes a strict timeout on outbound calls from Architect regardless of the backend configuration. The flow execution does not wait for the full 30 seconds if the internal gateway limit is hit earlier.

• Architect node timeout settings
• Platform-wide API latency limits
• Payload size restrictions for Data Actions