Uipath Assistant errors

Hi all, just a general ques… my colleague is having issues running an automation thru UiPath Assistant. It keeps throwing errors for different fields on the site where she’s downloading the report. She has tried running it several times and has been unsuccessful. Her teammate has no issue running it, it’s just her getting the errors. Below is an example of what she’s receiving. Any suggestions on how she can get this fixed. Thnx!

Hi @jennifer.x.mora

Open UiPath Studio and check selectors in UI Explorer. Adjust selectors using wildcards if needed. Update dependencies and packages in UiPath Studio. Compare screen resolution and browser settings with the teammate. Run UiPath Assistant as an administrator. Clear browser cache and restart UiPath. Run the process in Debug Mode to check logs. Try running the automation on another machine.

If you found helpful mark as a solution. Thanks

@jennifer.x.mora,

The error occurs when it failed to identify an UI element like button, text box etc.

On other user machine it’s working but another not this indicates that the selectors are not concrete here.

Try making your selectors more reliable and as much dynamic as possible.

Here are the key points for making UiPath selectors concrete and dynamic:

Use Variables: Incorporate variables into selectors to dynamically adjust parts of an element’s attribute.

Anchor Base: Use anchor elements with static identifiers to locate nearby dynamic elements.

Partial Selectors: Combine concrete parts with other dynamic identifiers.

Wildcards: Implement * and ? wildcards to handle dynamic attribute values.

Regular Expressions: Apply regex for complex dynamic scenarios.

UI Explorer: Utilize the UI Explorer to build precise selectors by examining detailed properties of elements.

ok we’ll try this, quick ques… i am the one who built this auto, but i dont use it at all. it was handed over to my colleague to run once a month. so if i do all the troubleshooting you have suggested on my studiox, will it fix her issues when she runs it? or does she need to open her own studiox and perform all troubleshooting steps? please advise :slight_smile: ty

Great @jennifer.x.mora

If you troubleshoot and fix the automation on your StudioX, it should work for your colleague if she’s using the same environment. However, if she runs it on a different machine, she should also check dependencies, settings, and selectors on her own StudioX. It’s best if she opens it and runs a test on her end after your fixes.

Pls mark as a solution if you found helpful. Thanks

ok cool ty :slight_smile: we’ll try that and i’ll get back to you if it worked or not :+1:

1 Like

I would suggest you better capture the elements from your colleague machine if it is possible which would be an easy fix.

Reason for this error could be that the selectors might contain values specific to your user or machine. If you have knowledge in modifying the selectors - Remove dependent properties from the selectors and make it generic. You can use wildcards or other constant properties to make it generic

You can even share the selector properties here for our analysis