We’re hitting a weird limit with web messaging data actions. Architect flow - simple enough - receives a chat transcript, transforms it, then POSTs to an external system via a data action. The data action uses a basic HTTP POST to /api/v2/conversations/{conversationId}/messages. It worked fine initially, but now payloads over ~2000 characters are getting truncated. No error returned in Architect, the data action just… sends a partial message.
The external system confirms it’s receiving incomplete payloads. We’ve checked the transformation logic, and it’s clean - no accidental string manipulation. The data action config has the content type set to application/json. We’re on client_app_sdk version 48.0.0.
The documentation doesn’t specifically call out a payload size limit for that endpoint. It does mention a general 2MB limit for data uploads, but that seems unrelated to a POST request body. I’ve seen some older forum posts suggesting a 4KB limit, which can’t be right - we pushed 3000 chars through before.
Here’s a sample payload that fails to send completely:
{
"customFields": [
{"field": "chat_transcript", "value": "This is a very long chat transcript that exceeds the apparent payload size limit. It includes a lot of customer details, agent notes, and troubleshooting steps. We need to ensure the entire transcript is sent to the external system for proper reporting and analysis."}
]
}
Anyone else running into this? Is there a hidden configuration somewhere, or is this a hard limit we need to work around by splitting the payload?