Periodically the JCP's return error code 422 on ert calls. Something like the following is seen in the JCP logs:
20220711/133508.439 - 57767 U00045098 Method 'GET', URL: 'http://server.domain:8088/ae/api/v1/100/executions/98870117/ert', received from IP: 'AWI.IP.Address'
20220711/133508.441 - 57767 U00045105 Log on of 'USERNAME/DEPT' successful.
20220711/133508.445 - 57767 U00045099 The server replied with following status: '422'
How can the cause of this be found?
Release : 12.3, 21.0
The http response of 422 is "422 Unprocessable Entity" which is a response status code that indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it is unable to process the information returned.
If this error is seen, the best way to find the cause is to go to the URL in the error message - in the example above this is http://server.domain:8088/ae/api/v1/100/executions/98870117/ert
This will give the results that the JCP is receiving, like this:
{ "code" : 1, "error" : "Critical paths can only be calculated for tasks that are not in an 'ENDED' state.", "details" : "Critical paths can only be calculated for tasks that are not in an 'ENDED' state." }
This should give an idea of what is being returned that does not work correctly