https://answers.axonivy.com/questions/4269/multiple-exceptions-lead-to-ivy-error-loop<p>Hi there</p> <p>We get an "ivy:error:loop" exception by Ivy in a loop. In this loop, we send some ws calls in a Callable Sub. Possibles exceptions are not handled in the Callable Process, but are caught by a "Inscribe Error Boundary Event" on the Callable Sub Element. The loop-exception occurs when we receive an exception (ivy:error:webservice:exception) in this Callable Sub twice.</p> <p>From our point of view one task could easily receive more than one identical exception during its execution. Ivy should not send a loop-exception in this case.</p> <p>Why does Ivy react like that? Have we done something wrong?<br> Is there a solution or workaround for our problem?</p>enMon, 16 Dec 2019 05:13:54 -0500https://answers.axonivy.com/questions/4269/multiple-exceptions-lead-to-ivy-error-loop/4282<p>You can prevent the error with a work-around: </p> <ul> <li><a href="https://answers.axonivy.com/questions/3181/prevent-by-pass-ivy-error-loop">https://answers.axonivy.com/questions/3181/prevent-by-pass-ivy-error-loop</a></li> </ul> <p>There is also an issue (XIVY-2219) that asks for API to explicitly reset errors by custom conditions. It's on the roadmap for the next leading edge version - though with low priority and therefore with no guarantee to be included in the next release.</p> <p>I'd prefer a custom API which allows the user to apply error reset behaviour for his custom need over a fixed scenario. Actually, Ignoring multiple errors of the same type might be a good idea for your situation, but totally unacceptable for other customers. So, if we change it, then with API that allows less more flexibility rather than a general new strategy for all. </p>Reguel WermelingerMon, 16 Dec 2019 05:13:54 -0500https://answers.axonivy.com/questions/4269/multiple-exceptions-lead-to-ivy-error-loop/4282