custom error not caught

Yoshiki Koiwa

I implemented a mechanism to catch errors occurring in Rest Client with Error Start and throw them as custom errors to be caught by higher-level processes. However, the custom error is not being caught, and the process is stopping. It's not always failing though; sometimes restarting Designer or editing unrelated parts of the project allows the error to be caught as expected, or it might start failing again. I referred to the "Catch default ivy error locally and propagate as custom error" in the error-handling-demos, but I'm unsure why it's failing. Can you identify the cause?

SocketTimeoutException: Read timed out
ProcessingException: java.net.SocketTimeoutException: Read timed out
BpmError: ivy:error:rest:client
BpmError: orchestrator:timeout
RequestException: orchestrator:timeout
Problem while processing request 'http://localhost:8081/designer/pro/ui-path-tools-for-automation-cloud$1/18F51607AF638B8D/18F51607AF638B8D-f3/resume.ivp'

Lukas Lieb

Hard to say why it is not working...
I quickly build an example similar to yours, and it seems to work always.
Also the error-handling-demos seems to work fine.

Normally I would say the most simple solution is that the error names are not 100% the same. And make sure that the error which is thrown is really the display label, because that does not need to be the case!
Also good to know is (and what you can try):

Catch the orchestrator:timeout error via a BoundaryErrorStart (it does not need to have a signal set, if it does not have a error defined, it will catch every error inside of the callable sub process)
You can also work with a more "global" error catch code, in your case the code "orchestrator" should also catch the code "orchestrator:timeout"

Also can give our doc maybe a hint what is wrong: https://developer.axonivy.com/doc/10.0/concepts/error-handling.html

Can you build a simple demo project, where you can reproduce this problem and which you can share?
On which version does this problem occur?

Yoshiki Koiwa

I have confirmed that the error name is correct.
I have created a demo project that confirmed that a similar phenomenon occurs in my environment, so I would like to share it.
The version is confirmed to be 11.2.1.
https://community.axonivy.com/assets/files/2024-05-13/1715566243-287792-errorcatchdemo.zip

hohhashi

file upload test

Yoshiki Koiwa

This has been fixed because the link was not displayed correctly. Sorry, please get the file from the link above.

Lukas Lieb

Thanks, I will check it 👍️

Reguël Wermelinger

Hi,
did you see that it is also possible to fire concrete bpm-errors directly on the RestClient Activity?
We can write custom codes to be thrown under reponse/error handling, to avoid modeling an explicit boundary-catcher and wrapping of the original error. Maybe this solution is also preferable, as your models get less technical and can focus on the business-model.

Lukas Lieb

I think I finally understood what the problem is.
We support the creation of a so-called "Project Error Process". This is a "global" process that can catch errors over different processes.

There is also an example process in our error-handling-demos:

I think your problem is only that your sub process is prefixed with "Error". If you call your sub process e.g. "Timeout" then it should work:

However with Ivy 8.0.x there was at least the hint that this process had an Error Icon and since 10 this is sadly no longer the case. And also I think we should prevent the creation of such error processes as sub or ws process. So I created an Issue (XIVY-14140) to fix this.

Yoshiki Koiwa

thank you. However, the demo project I sent used a subproject with a name starting with Error, but the original project where the error occurred used a different name, so the cause seems to be different.
However, it seemed like the problem could be resolved by using Rest Client's error handling, so I decided to proceed with that method.