Under what scenerio can the [Check True] activity be used in the [Retry Scope]?

For the [Check True] activity, the UIPATH Documentation states:

This activity can be used in the Retry Scope activity.

I am finding that this activity can not be placed into the [Condition] block of the [Retry Scope]. Although, it can be placed in the [Action] block. This is not surprising because I would imagine that most activities can be used in the [Action] block.

I would assume that since this statement is even mentioned at all is because the documentation was trying to say that the [Check True] activity can be used in the [Condition] block.

What is the case for this? Can the [Check True] activity be used in the [Condition] block of the [Retry Scope]? If so, how can I get this done

You can instead use the “is true” or “is false” activities instead. I believe it is the microsoft activities package

Thanks. I already figured that out.

There seems to be a lot of misinformation in the UIPATH documentation.

How were we supposed to know that? Your very last sentence asks how to “get this done” so I offered an alternative.

The reason why it doesn’t work is a limitation of microsoft workflow foundation that uipath is built upon. This particular activity requires an input of activity(bool), rather than outargument(bool). Unfortunately there’s no easy way to tell if the boolean you get from any particular activity is activity(bool) or outargument(bool), so it’s a bit of a guess & check situation.

I’m not sure why uipath never changed the retry activity to accept either of them, but it must be difficult because there have been many threads complaining about the issue over the years

@Dave

I figured out the same solution that you provided, but I still wanted to find out if I was misunderstanding something about what I read. I was not looking for an alternative to the [Check True] activity, but how to use it as described in the UIPATH documentation.

I asked "how to get THIS done” - not an alternative to THIS.

Hi,

I think Check True/False activity is useful and readable for retrying the process at the middle of it in some case as the following, because condition of retry scope is only checked at the end of retry scope.

Regards,

@Yoichi

Thank you!

In playing around with the [Check True] as you described - it appears to “short circuit” the [Action] block - similar to the [Break] activity in a [For Each] loop.

I think that I understand and I see 2 benefits of this:

  1. Save time - by ending the process when you know that it is doomed to fail anyways
  2. Provide a more meaningful exception message

Are there any more benefits that you know of?

Thanks,

John

It short circuits because it throws an error when it’s not true. Retry scope will retry when an error is thrown during the action block

Hi,

To use Check True/False, it makes workflow simple and readable. (Although we can also describe it using IF and Throw activity.) This means it helps to improve maintainability. It’s one of important benefits, I think.

Regards,

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.