You are calling the Computer Vision server too often

So after about 100 loops / 222 it threw an error. “You are calling the Computer Vision server too often” Why is there a cap on this, I’m not sure how I’m supposed to continue my work if there’s limitations on how many times I can call the CV server within x amount of time.

1 Like

I’m also seeing “You are calling the Computer Vision server too often. [429]” It would be really useful to know the limitations around this knowing this i could delay my workflow steps.

I contacted their support directly but got no clear answer to what the limitations are around the CV server. Maybe you have better luck figuring it out.

Hi Dabar,

I believe that Computer Vision is still in the Beta stage and is not recommended to use it for live/production usage.

1 Like

That’s right it is infact in beta stage and that’s why I’m not using it in production :smiley: I had to figure out another way of doing it but it would still be nice to know the limitations of the CV server to experiment and work towards a production ready RPA solution.

1 Like

You can check on this thread. Seems it is possible make the Computer Vision offline.

Thank you! I’ll definitely look into that

Hi Dabar,
I’ve been advised its 15 calls per minute, hope this helps.

1 Like

Yes for the moment the cap is at 15 calls/min but the throttling mechanism will change during the beta period

Is this cap per robot or per machine or per ?

Per IP

Also please try the latest version (1.0.1) from the official feed and let us know if you still run into this issue.

Thanks, improvements have been seen. My biggest issue now is looking for messages or pop-up that might exist when they are not found.

I will try that update now.

After this update, not seeing any more of this error:
< You are calling the Computer Vision server too often. [429] >

but now experiencing high level of another error in CV activities that were previously working:
< UiPath.CV.ElementNotFoundException: Element not found >

This is occurring within AnchorContextAware activities for Anchor / Target activities that are valid before and after running in the workflow that is giving this error.




Hmm, so you’re saying that there’s a valid anchor/target pair, that works fine at design time and fails at runtime?
Are you sure the UI is the same in both situations?

What app are you automating?

Yes, UI is the same.

Since updating Studio to 2019.4.3 the error message have changed from [ You are calling the Computer Vision server too often. [429] ] to [ Element not found ] after the update. As I understand the change, now calls to CV server will not repeat if elements are not found as they did in previous versions.

This application is MEDITECH and accessed via VMWARE.

yes that’s normal. Basically the error you got was because the element was not found and the detection was retried too often till it hit the throttling limit. Now it’s just not found and you need to fix it.

When an element is not found, a refresh is still done automatically in case it appears, only a bit slower.

Also, I recommend to update Studio to the LTS version (18.4.5+)

Hi Cosin

Is this still a limit of 15 calls pr minute?


Hi @petterws

For the ComputerVision cloud server we have a limit of 30MP / minute for Community users and 240 MP / minute for Enterprise users.


Thanks @sbotan