Using Input mode: Simulate (click), my Click activity correctly clicks a Java popup menu item that opens a modal Java dialog. However, the UiPath workflow stops on this Click activity for 60 seconds and then generates a “Click generic error” before continuing as desired (Even though it executed, there is no trace statement entry for this Click event). I understand this behavior could be related to using Simulate Click (the other click types do not work for this case).
How can I prevent (or diagnose) this Generic Error?
Is this something that can / should be fixed in a future release?
How can I set a shorter timeout for the Click Activity (Modern)?
I tried changing the project and the Click activity timeouts to a short timeout, but these values appear to be ignored by the Click activity.
Additional Info:
Windows 11
UiPath.UIAutomation.Activities: v22.4.4
UiPath.System.Activities: 22.4.1
Hi @grosner
You came across an interesting case. The click opens a modal, and the app itself waits for the modal to close, without providing an “answer” back to the Studio. This can only happen with Simulate, and is handled in our code, but it is not exposed so nicely.
To work around the problem:
Use a FindElement activity and store the object. Let’s call it elem.
Use an assign block, or InvokeCode to set elem.UseNonBlockingInput to True.
Use the click activity (classic) to pass elem as the target for the activity and be sure to check the Simulate flag on that activity.
Let’s check if it works.
Now, for the questions:
The workaround will help you to prevent the problem from happening.
The UX can be improved, but the background solution would be the same.
There is the Timeout property on the activity, but the timeout you are talking about is a communication timeout, which, in ideal conditions, should never be reached. I am not sure it can be changed from the UI.