• The object wait setting is applicable to every built-in action that contains the control argument and expects the specified control to exist.
• The object wait setting does not apply to does/if built-in actions: specifically, if control exists, if control not exists, and does control exist. For these three actions, use the window wait probe setting.
• Setting a high wait time value may negatively impact test performance.

Suppose you are using check control exists and check control not exists built-in actions, the execution mechanism is as follows:

1. TestArchitect starts looking for the specified window.
2. If the specified window is not yet available, TestArchitect waits until the window is available within the default timeout 20 seconds, specified by the window wait built-in setting.
3. When the timeout is reached but the window is still unavailable, TestArchitect reports a warning informing that the window could not be found (No pass or fail is recorded).
4. If the window is found, TestArchitect starts looking for the specified control.
5. With the check control exists action:
1. If the specified control is unavailable, TestArchitect waits until the control is available within the default timeout 20 seconds, specified by the object wait built-in setting.
2. When the timeout is reached but the control is still unavailable, TestArchitect reports a failed message.
6. With the check control not exists action:
1. If the specified control is available, TestArchitect waits until the control is unavailable within the default timeout 20 seconds, specified by the object wait built-in setting.
2. When the timeout is reached but the control is still available, TestArchitect reports a failed message.