Hello everyone! I am super excited to be building out a new integration between Genesys Cloud and our AWS environment using the Lambda Data Action integration. We are trying to pull back a fairly large customer history object (about 45KB of JSON) to use for some dynamic routing decisions in Architect.
However, we are consistently hitting the 10 second timeout on the Data Action side, even though our Lambda function is finishing in under 2 seconds. It seems like the Genesys side is struggling to parse the response or maybe we are hitting a limit I do not know about? Has anyone else pushed large payloads through the Lambda integration? We are using the standard JSON-RPC pattern. Any advice would be incredible!
I am honestly so tired of dealing with these Data Action ‘features’. It is not just you. The Data Action service has a strict 64KB limit on the response size, but it actually starts choking long before that if you have deeply nested objects.
If your 45KB is one big array of objects, the parser will take forever. I spent three days last week debugging a similar issue where the action would just hang and then time out.
Genesys needs to fix their backend parser performance because it is unacceptable.
Hey there. I am an admin for a 800 agent org in Tokyo. We had this problem when we moved from CXone.
What we did was we used a Velocity template to filter the data on the Genesys side before it gets to Architect. You should only map the fields you actually need in the output contract.
If you try to map the whole 45KB object, it will time out every time. Just map the 3 or 4 fields that matter for your routing and let the rest go.
Hope that helps!