Start Process returns error 502 Bad Gateway
SummaryStart Process returns error 502 Bad Gateway
Within an action chain, we are calling Start Process and passing to it a number of parameters in the payload. Payload below.
The process starts properly and we read the ProcessId from the response, but when the payload reaches a certain number of characters (exceeding 2427), the network returns a 502 Bad Gateway error. Under the covers, the process was started correctly, but we do not know that from the 502 Bad Gateway error.
The same payload that creates this issue can be tested in Postman and returns a successful 200 OK.
Has anyone seen this behavior?