Hi Team,
How to ensure my UiPath bot is more resilient and robust. Please share your list of thoughts on this. Thanks.
Hi Team,
How to ensure my UiPath bot is more resilient and robust. Please share your list of thoughts on this. Thanks.
Use REFramework or a modular setup – makes exception handling, retries, and logging much easier to manage.
Always wrap critical parts in Try-Catch and log the error message + stack trace so debugging is simpler later.
Validate inputs before using them (null checks, empty strings, etc.) – this alone prevents so many random crashes.
Don’t rely on fixed delays; use Check App State / Element Exists / Retry Scope instead.
Make your selectors dynamic and stable – avoid indexing and use wildcards or anchors.
Use Orchestrator queues for item-level retry and better error tracking.
Separate system vs business exceptions so you can reprocess cleanly.
Keep configs, credentials, URLs, etc., in config files or Orchestrator assets (never hardcode).
Add proper logging (Info/Warn/Error) at key points so issues can be traced easily.
And finally – test with real data and network conditions. A bot that runs fine on your dev machine might fail when latency or pop-ups appear in prod.
Thanks Chandresh. Can you elaborate this below point
Don’t rely on fixed delays; use Check App State / Element Exists / Retry Scope instead.
Thanks. Need one more clarification
How to ensure that RPA/UiPath automation is feasible for the given app ? (feasibility study)
Is there any list of points/checklist to check whether UiPath automation can be performed or not ? From Architect level what all info we need to check?
Hi @Honda
Here are a few points:
Always let your bot wait for screens or elements properly using “Wait for Ready” or “Check App State.” It helps the automation adapt to real-time behavior instead of relying on fixed delays.
Use stable selectors and anchors so small UI changes don’t break your bot. Avoid attributes like indexes or long, changing selectors.
Wrap important actions in Try/Catch blocks, add clear log messages, and set up a Global Exception Handler for unexpected issues. It’s always better for a bot to recover gracefully than to fail suddenly.
Store all your URLs, credentials, and timeouts in Orchestrator Assets or config files so you can easily update them without modifying the workflow.
Process data using Orchestrator queues and handle items one by one. This way, even if one transaction fails, others can still continue smoothly.
Record what’s happening at every step with good logging and screenshots. These make troubleshooting and debugging much faster.
Test your automations with real-world and edge-case data in the same kind of environment they’ll run in production. It helps you catch hidden issues early.
Always have a fallback plan — for example, if a click fails, try a search box, a shortcut, or another navigation method.
Build smaller, reusable workflows with clear inputs and outputs. This makes your bots easier to maintain and update later.
Take advantage of UiPath’s latest features like - Healing Agent and Object Repository — they help your bots automatically adjust when the UI changes.
Depends on use case to usecase. Some overview -
Thanks, Chandresh this helps
Thanks for the info.
How this works? Is this an option in properties or a separate activity ?
It is property for all Ui related activity
am searching that property in click activity. Under which option it will come?
Thanks this helps for better understanding
We can use this Object Repositories only in this version 2024.2.1
We can’t this option in 2020 or in 2022 versions?
Yes, for more clarity please refer the below documentation:
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.