Context:
Running Genesys Cloud v2023.10 with a custom Architect flow for SMS digital channels. The objective is to trigger a ServiceNow incident upon high-priority keyword detection. The webhook payload is constructed via a Data Action, mapping the text field and conversationId to ServiceNow REST API parameters. Locally, the payload validates perfectly against the ServiceNow schema, and standard HTTP POST tests succeed with a 201 Created response.
Question:
Can anyone clarify why the Genesys Cloud Data Action logs a 400 Bad Request specifically when the short_description field exceeds 150 characters, despite ServiceNow accepting up to 4000 in the incident table? The error response body from ServiceNow indicates Invalid value for field short_description, yet truncation logic in the flow prior to the Data Action step is not being executed as expected. Debug logs show the payload arriving intact at the Genesys edge before the 400 is returned. Is there a hidden character encoding issue or a specific Genesys Cloud limitation on payload size for outbound webhooks that overrides the ServiceNow schema? Checking the x-gc-request-id headers reveals no further insight. Need to determine if this is a flow logic error or a platform-level constraint on the Data Action output.