I am getting this warning somewhere from the process.
Execution with id ‘{}’ throws an error event with errorCode ‘{}’, but no catching boundary event was defined. Execution is ended (none end event semantics).
Unfortunately, since it was a batch processing, I am unable to reproduce this behaviour and I also can not detect from which ServiceTask of my process this came from.
I already check in all my processes, they do catch exceptions, if they occur.
Can someone explain when this error generally occurs?
If for example a NullPointerException happens in the java code, that exception would be wrapped in MyException. And in the process, MyException will be catched from the process.
Execution with id ‘{}’ throws an error event with errorCode ‘{}’, but no catching boundary event was defined. Execution is ended (none end event semantics). Is this message reliable as it states? Or is this a high level message, which root cause still needs to be analysed?