Logistics client is pushing a 42KB context object into a custom data action for inventory lookups. Architect UI marks the execution as “Failed” instantly. Clicking the details reveals a 422 Unprocessable Entity, yet the error message field is blank. It’s just an empty string.
Payload’s likely the trigger. Stripped the nested shipment history arrays down to 10KB, and the action completes without a hitch. Request body limit must be tighter than the 256KB response limit mentioned in the docs.
Logs in the data action monitor truncate the JSON after 500 characters. Debugging’s doing jack all right now. Flow just hangs on the “Wait for Data” block. Mic stays hot while the 30-second timer bleeds out. Callers get dropped straight to the operator queue. Containment metrics tanked by 15% last night because of this.
Region is eu-central-1. Architect version 2023-12-28.
Response payload from the execution endpoint:
{
"status": "failed",
"statusCode": 422,
"message": ""
}
Validation error is completely silent here.