I have a process on a mainframe and using click activities to navigate to specific words.
The classic activities use to have a click ocr text. Would select the range and input the word I want to click in. I have migrated away from the classic activities and using the normal click now. The CV picks up the fields on the mainframe and the click happens in roughly 3 seconds. Which is perfect. There are cases when I use the click. Same method. Same setup as the 3 seconds one. But then the click takes 18 seconds to actually do the click. If I take that click. Create a separate sequence to test it. It happens in 3 seconds roughly. But when I run the process through my RE-Framework. It always take around 18 seconds. Then one screen later or the text just above that click. Those are 3 seconds but there is just some spots that takes super long. Unsure why this is happening.
Also no similar wording on the screen. Using computer vision anchor as well. tested with it and without it. Same speed issue
Any ideas?
After testing update. When the click happens on the mainframe. Its using the CV for the click. The first one seems to be fast but the that follows is very slow. This a computer vision limitation on the click activity itself?
Note not using the CV activities
hey @Etienne8125
Solution is Use CV ‘Find Image’ + Click, which work Faster
Instead of direct Click with CV, use:
Find Image Activity (CV) → Get coordinates → Click on coordinates
Why is image detection separate from click action? Because it’s much faster, speed improvement of 3-5 seconds, even in RE-Framework
For mainframe, general recommendation is to use the terminal activities within UiPath however if your are using I would check below
this may not be a CV limitation directly. Since the same click is fast when tested separately but slow inside REFramework, I would first check the activity settings and what is happening before that click.
A few things I would look at:
Check the Timeout and WaitForReady settings on the Click activity.
Try setting WaitForReady = None or Interactive and test again.
Make sure there are no retries, delays, or element checks happening before the click in REFramework.
Check if the screen is fully loaded before the slow click runs.
Try adding a small delay or a proper “Check App State” before that click, so UiPath does not keep searching/waiting.
If CV is involved, try refreshing the target or re-indicating that specific element.
Since it works fast in a separate sequence, I would suspect the issue is more related to the workflow context, timing, or activity wait behavior rather than the click itself.