In UiPath Studio, the “WaitForReady” and “TimeoutMS” properties are crucial for controlling the behavior of activities when interacting with UI elements.
WaitForReady Property
The “WaitForReady” property determines when the activity should start executing based on the readiness of the target UI element. It has three options:
- None: The activity does not wait for the UI element to be ready and proceeds immediately.
- Interactive: The activity waits until the UI element is partially loaded and ready for interaction.
- Complete: The activity waits until the entire UI element is fully loaded and ready for interaction12.
TimeoutMS Property
The “TimeoutMS” property specifies the maximum amount of time (in milliseconds) that the activity will wait for the UI element to be found before throwing an error. The default value is 30,000 milliseconds (30 seconds)13.
Behavior with WaitForReady Set to Complete
When “WaitForReady” is set to “Complete,” the activity will wait for the entire UI element to be fully loaded before proceeding. Regarding your specific questions:
- Does the timeout count start before the wait starts to move until it is ready?
- No, the timeout count does not start before the wait. The timeout period begins when the activity starts executing and waits for the UI element to be ready4.
- After the wait starts to move until the preparation is completed, does the timeout count start?
- Yes, the timeout count starts when the activity begins waiting for the UI element to be fully loaded. If the element does not become ready within the specified timeout period, an error will be thrown4.
Verification
To verify this behavior, you can:
- Log Messages: Use logging activities before and after the activity to check the timestamps and confirm when the waiting period and timeout start.
- Adjust TimeoutMS: Set a shorter timeout period and observe if the activity throws an error after the specified time.
LLM helped me to write this but it’s validated me.