In my case, the error occurs because the window to operate type into does not come out.
In normal situations, the window will definitely appear to operate type-into.
However, in exceptional circumstances, the input window does not appear.
Hi,
Here is a suggestion, a template I created for your scenario. (UiPath Project Attached below )
Basically controlling all the flow using try catch and assigning to a error variable, so any error occurred inside of sequence A will redirect to sequence D before continue to sequence B, if no error then it goes directly from A to B.
The entire activity is like this right now. I have to return it to the state before download CheckAppstate. Or I have to discard the entire workflow I created.
I create workflow based on UiPath.UIA Automation.Activities.If I go down to use the activity you told me, the existing activities are ruined. I checked the packages of other workflows and downloaded them again.