Hi there

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.

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.

Why does Ivy react like that? Have we done something wrong?
Is there a solution or workaround for our problem?

asked 11.12.2019 at 09:41

Adrian%20Imfeld's gravatar image

Adrian Imfeld
46191320
accept rate: 77%

edited 11.12.2019 at 09:42


You can prevent the error with a work-around:

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.

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.

link

answered 16.12.2019 at 05:13

Reguel%20Wermelinger's gravatar image

Reguel Werme... ♦♦
9.4k21857
accept rate: 70%

edited 16.12.2019 at 05:54

My WebService calls are already in explicit callable subs. If I get you right... my Inscribe Error Boundary Event on the Sub Call Element is the problem. I should move even that in a callable sub or dealing with the exceptions in my existent callable process? Anyway, we are looking forward to the API you have planned.

(16.12.2019 at 10:19) Adrian Imfeld Adrian%20Imfeld's gravatar image

Yes, if you move the exception handling into the callable process: next to the ws-call that causes the issue, then you can brake the loop. To be precise, ws-call activities act as loop breaker for errors that are handled within them.

(16.12.2019 at 11:29) Reguel Werme... ♦♦ Reguel%20Wermelinger's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×48
×8
×3

Asked: 11.12.2019 at 09:41

Seen: 322 times

Last updated: 16.12.2019 at 11:29