Do you have the errorCodePath header set in the Worker Activity?
The Github links shows that if this error is found, it will throw a BPMN error, rather than failing. The Job Fail isn’t a BPMN error, but a technical error, which is why it’s not getting caught.
You can think of this as similar to a try…catch
try {
…
} catch BusinessError {
…
}
But, since the worker is throwing TechnicalError, the process doesn’t go down your catch block.
I found also a bug in the http-worker if you errorcode is an int value like 404. For example if my spring boot api return ResponseEntity(HttpSatatus.BAD_REQUEST);
the parser fail and the returned value is null. For fix this you can replace the method extractPath :