Skip to main content

So we have workspaces to run the bot unattended, So I have strange problem that I’ve encountered that is new to me, the problem is  when I execute the bot in workspace it doesn't capture the ui elements in the website in workspace but in my actual device it works, I found a solution by restarting the workspace the bot is capturing the element well,  but then again after few runs or few hours the issue persists again.

Hi @Kyte ,

 

It sounds like you’re encountering an intermittent issue with UI element capture in Automation Anywhere A360 when running bots in a workspace. Here are some steps and best practices that might help resolve this problem:

 

  1. Clear Browser Cache: Regularly clear the browser cache in the workspace to ensure that old data isn’t interfering with the bot’s ability to capture UI elements.
  2. Restart Browser: Restarting the browser can sometimes resolve issues with UI element capture. This is similar to your current workaround of restarting the workspace.
  3. Check Browser Versions: Ensure that the browser version in the workspace is compatible with Automation Anywhere A360. Sometimes, newer versions of browsers can cause issues. If necessary, downgrade to a supported version.
  4. Update Automation Anywhere: Make sure you are using the latest version of Automation Anywhere A360, as updates often include bug fixes and improvements.
  5. Review Bot Code: Double-check your bot code to ensure there are no issues with how UI elements are being captured and interacted with.
  6. Error Handling: Implement robust error handling in your bot to manage scenarios where UI elements are not captured correctly. This can include retry mechanisms or alternative workflows.
  7. Check Browser Zoom Level: Ensure that the browser zoom level is set to 100%. Different zoom levels can affect the bot’s ability to interact with UI elements.
  8. Verify Automation Anywhere Plugin: Make sure the Automation Anywhere plugin is installed and enabled in your browser. This plugin is essential for the bot to interact with web elements correctly.
  9. Check Screen Resolution: Ensure that the screen resolution of the developer VM and the bot runner VM are consistent. Differences in screen resolution can impact the bot’s ability to capture and interact with UI elements correctly.
  10. Check UI Objects’ Attributes: Always find unique attributes for UI objects or use relative DOM XPath to ensure the bot can reliably identify and interact with the elements.

Best Practices:

  • Regularly clear the browser cache and restart the browser.
  • Ensure compatibility between your browser version and Automation Anywhere A360.
  • Implement error handling to manage intermittent issues.
  • Keep the browser zoom level at 100%.
  • Verify that the Automation Anywhere plugin is installed and enabled.
  • Maintain consistent screen resolution between the developer VM and the bot runner VM.
  • Always find unique attributes for UI objects or use relative DOM XPath.

If these steps help you resolve the problem, please mark it as answered. If you need further assistance or have other questions, feel free to ask!

 

I have tried all the solution you provided but the error still persist. Our bots has not been encountering this issue for the past 10months, only last week after we had workspaces reboot, its weird because when this happened I normally restart the workspaces and it works but its not convenient this way to restart the workspace whenever the issue happened.

Reply


Terms & ConditionsCookie settings