topic Re: Escape from Repeat Based on condition in Workato Pros Discussion Board

Escape from Repeat Based on condition

prp_proton — Fri, 15 Sep 2023 09:39:47 GMT

How to escape from a repeat loop in workato when a specific condition is met? Repeating entire list and check condition is bad for the performance.

I don t want to use monitor functionality and throw error to escape from the loop.

is there any alternate solution present?

Re: Escape from Repeat Based on condition

gary1 — Mon, 18 Sep 2023 17:46:38 GMT

There are different options, but it depends on your input and what you're trying to accomplish. If you can provide more info we can probably make a few suggestions.

Re: Escape from Repeat Based on condition

sampath — Mon, 18 Sep 2023 21:46:19 GMT

I usually write python or ruby module for that purpose.

Re: Escape from Repeat Based on condition

prp_proton — Tue, 19 Sep 2023 05:51:23 GMT

Hi,

I am just looping over a repeat helper list which is of size 100(size is unknown). Inside the loop, I am calling salesforce. Based on the SF response, when a flag is true, I want to exit from the loop and do the other processing's.

I don't want to create 100 tasks, when I might require to exit after 5 tasks. This is the scenario.

Re: Escape from Repeat Based on condition

prp_proton — Tue, 19 Sep 2023 05:54:52 GMT

So, do I need to do the entire loop processing inside the ruby module or in ruby, there is an option to exit from the workato provide repeat action?

Re: Escape from Repeat Based on condition

gary1 — Tue, 19 Sep 2023 17:25:19 GMT

If you're calling SF within the loop and you need the SF response/flag to break the loop, then the simplest way to accomplish this is to use the error monitor. It does exactly what you need and will not process the full list once the loop is broken. You can configure it so it does additional processing after the catch/break.

Is there a reason don't you want to use the error monitor?

Re: Escape from Repeat Based on condition

sampath — Tue, 19 Sep 2023 21:37:42 GMT

I wanted to limit the iterations. So I used ruby while loop or take_while loop . it helped me to avoid looping through all the items in the list. ( we do not have return or break options )

if you need further help, please let me know. Happy to help

Re: Escape from Repeat Based on condition

javier-riesco — Wed, 20 Sep 2023 08:13:01 GMT

Another possible workaround to this is to utilize a Recipe Function. Within the Recipe function, include the necessary loop and condition. Once the condition is met, use the Return function to exit the Recipe Function and return to the parent recipe.

Re: Escape from Repeat Based on condition

mppowe — Wed, 20 Sep 2023 14:08:15 GMT

Yea I agree about the Monitor/Error block. I resisted using it at first b/c it felt un-intuitive and a bit of an eyesore for this purpose, but I embraced it b/c it's easy. The recipe function idea is a good one too, but you may want to save the task usage if you'll be calling this recipe (and/or the function) many times.

Re: Escape from Repeat Based on condition

javier-riesco — Fri, 22 Sep 2023 12:33:57 GMT

The content has been removed for clarity purposes.

Re: Escape from Repeat Based on condition

mppowe — Thu, 21 Sep 2023 12:48:36 GMT

Javier,

It has always been my understanding that calling a Recipe Function consumes a task. It was a big bone of contention for me when I found out and I brought it up to my CSM multiple times. I've never heard back that it didn't consume a task. When I read your post I thought maybe Workato had changed its policy to ignore those actions now, but in looking at a job this morning it still seems to be consuming a task:

Re: Escape from Repeat Based on condition

marlon-muela — Fri, 22 Sep 2023 10:04:40 GMT

Hi @prp_proton ,

It depends on your use case; for example, if you want to stop the loop after several lists or indexes, you can add a condition and a monitor action to move to the next step in the recipe. Here's an example:

Re: Escape from Repeat Based on condition

javier-riesco — Fri, 22 Sep 2023 12:35:07 GMT

mppowe

You are correct. Calling a recipe function will consume 2 additional tasks per loop: one when calling the recipe, and another for the Return action. Please refer to the screenshot below for reference.

Re: Escape from Repeat Based on condition

prp_proton — Fri, 22 Sep 2023 16:56:35 GMT

If we are using the catch break..... it will show error in the job report. which is actually misleading. Thats why looking some another solution.

Re: Escape from Repeat Based on condition

gary1 — Fri, 22 Sep 2023 17:10:46 GMT

If you're referring to the error monitor, it doesn't automatically mark a job as failed in the job report. The job viewer will still show which action had the error, but the job could be configured to stop successfully or failed.

Job report:

Job viewer:

Re: Escape from Repeat Based on condition

mppowe — Fri, 22 Sep 2023 17:22:53 GMT

@gary1 is right, I have recipes that catch errors but don't fail out. They handle the error then move on. In those cases the Job History doesn't show failure. The "Error Message" from the Catch block is populated, but that won't show anywhere unless you're exposing that in the Job History

Re: Escape from Repeat Based on condition

prp_proton — Mon, 25 Sep 2023 05:43:01 GMT

@mppowe, @gary1 : I mean to say, if we are monitoring the repeat step using try catch and based on the condition, want to get out of the loop, so when ever the condition match, the action will be marked as error to go to the catch block. I agree that in Catch block we can mark it as successful, but in the job history will is not show the action as RED MARK. is this appropriate to implement like this?

Also, if any real error happens inside the repeat (i.e connectivity issue to another system) that will also endup to the same catch block.

Re: Escape from Repeat Based on condition

mppowe — Mon, 25 Sep 2023 11:34:27 GMT

It will not show as a red mark unless the job fails.
When I throw the error to exit the loop, I use a specific error message. Then in the catch block, check for that message. D it matches, you move on, otherwise handle the unexpected error like normal. That way if you want to to fail it will.