Request for Documentation on UI Rendering/Latency Issues Affecting Filter Selection in UiPath Automation

Help Studio
1

Hello UiPath Community,

I am seeking guidance and support documentation related to a peculiar issue we’ve encountered in our automation process. For the past three years, our automation solution has worked smoothly in production without any problems. However, recently, we faced an issue with the Sample Set Checklist Review process where, due to incorrect filter selection, two out of seven checks failed when they should have passed.

Issue Details:

  • This issue occurred for only two sample set reviews. For all other cases, the filter selection has worked correctly.
  • The bot is designed to select a specific filter, perform a “down” and “up” arrow action to refresh the filter, delete the first row, and then enter the current sample set under review.
  • Despite logs showing that the correct filter was selected, it appears that due to possible UI rendering or latency issues, the bot landed on a different filter containing multiple data entries. This incorrect selection caused the bot to report a “Fail” instead of a “Pass.”
  • After this incident, the filter selection process has worked as expected without any further issues.

Request for Assistance:

  1. Documentation or Articles on UI Rendering/Latency Issues: Could you provide any UiPath support documents or resources that discuss potential UI rendering or latency issues affecting element selection, specifically cases where the logs might indicate the correct selection, but the UI hasn’t updated properly?
  2. Similar Incident Experiences: Has anyone experienced a similar issue where the bot incorrectly selected a different filter due to UI rendering delays or latency, even though the logs showed the correct filter was selected? If so, how did you handle it, and what measures did you take to prevent such occurrences in the future?
  3. Best Practices for Ensuring Accurate UI Interaction: Any advice or best practices on handling UI element selection to avoid such issues, especially in cases involving filter selection and dynamic data, would be greatly appreciated.

I would be grateful for any insights, documentation, or suggestions you can provide to help address this issue and include relevant information in our CAPA report.

Thank you for your support!

Best regards,
Rajesh

2

@rajeshmushini

Welcome to the community

  1. Use wait for load complete will help here
  2. Use check app state in combination with the visibility property so that the bot would wait till the complete ui is loaded and not only till interactive or the element that is needed
  3. This can avoid such latency related issues

Cheers