Issue with Try catch in UIPath Studio 2019.12.0-beta.61

Hello Everyone,

I am trying to perform some automation on SAP screens. In one of the area I am making use of a Try catch activity. The function of this activity is to Find a specific text using the “Find Text Position” activity in the Try block and once it is found it will set the flag to true using the Assign activity as show in the below picture.

The process will fail if the specific text is not found in the mentioned area using the “Find Text Position” activity in the Try block. In order to handle this i have placed 2 catches one with System Exception and the other with TextNotFound Exception. In these exceptions the process will perform a page down operation in order to scroll down as shown in the below picture.

Once the scroll down happens the whole process repeats again to search for the required text.

But when i run it the process is failing at the “Find Text Position” activity itself with the below exception.

“RemoteException wrapping UiPath.Core.Activities.TextNotFoundException: Text was not found
at UiPath.Core.Activities.FindText.EndExecute(NativeActivityContext context, IAsyncResult result) at UiPath.Core.Activities.AsyncNativeActivity`1.BookmarkResumptionCallback(NativeActivityContext context, Bookmark bookmark, Object value) at System.Activities.Runtime.BookmarkCallbackWrapper.Invoke(NativeActivityContext context, Bookmark bookmark, Object value) at System.Activities.Runtime.BookmarkWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)”

As per my knowledge the main functionality of the try catch is to go to catch block if the try block fails.

Can you please help me clarifying this issue. Thanks in advance.

FYI i am using UIPath Studio 2019.12.0-beta.61 community license

Thanks & Regards.

HI @UdayKiran ,

Welcome to the Community.

The order of the catch blocks seems to be the Issue here. As i can see in your screenshot -

Exception is coming before the TextNotfound Exception. So any exception irrespective of the type is getting handled by the exception block and not by the specific exception type.

Please Re-Order the Exception Blocks.
TextNotFoundException and then exception.