Hello, there is a problem when using the activity.
There are occasional exceptions when using type-into, which is when the element to type-into does not come out.
In this case, I’m going to use a try catch to deal with an exception
The sequence I wrote cannot be treated as an exception, and the workflow is interrupted by an error.
I would like to use try catch to deal with exceptions when type into error occurs.
It’s my first time using try catch so I don’t know what to do.
So till the saves as window comes up you want to click on the button?
If so then in the click activity you have a verify option…where you can indicate the type into field so that the click happens multiple times till the type into window is appeared
The download click button is disabled
Even if I press it, it doesn’t come out, so the storage window can’t come out.
That’s why I’m trying to move on to an exception.
The download click button is disabled
Even if I press it, it doesn’t come out, so the storage window can’t come out.
That’s why I’m trying to move on to an exception.
That is what happens…as mentioned just do a step into /continue and the control will then go to catch block…or run in run mode instead of debug it would move without stopping
What I want is as follows.
Sequnce
“A”, “B”, and “C”. Let’s assume that the order is “A”, “B”, and “C”
If an activity in ‘A’ sequnce error occur, the next rest of the normal activities in ‘A’ sequnce will not work(this is skip) because of the previous activity error, regardless of its own error occur or not.
Then
Instead of “A” Sequnce
The activities of ‘D’ Sequnce are working.
‘D’ Sequnce does not work in normal situations and only works in case of A error.
In this case, it will proceed in the order of ‘D’, ‘B’, and ‘C’.
Another way would be to use a check app state activity to check for save window…if window present then perform steps of A if not present perform steps of D