• The window wait setting is applicable to nearly every built-in action that contains the window argument. This built-in setting is used when it is expected that the specified window must exist.
• However, the window wait setting is not applicable to does/if built-in actions. That is, if window exists, if window not exists, and does window exist. Instead, the window wait probe setting is used for those three built-in actions.
• Setting a high wait time value may negatively impact test performance.
• For web automation, window wait goes into effect first, and then page wait does. In other words, TestArchitect first looks for the presence of the specified window. Once that condition is satisfied, TestArchitect waits the allotted page wait time for the web page to be rendered and available.

Suppose you are using check window exists and check window not exists built-in actions. The execution mechanism is as follows:

1. TestArchitect starts looking for the specified window.
2. With the check window exists action:
1. If the specified window is not yet available, TestArchitect waits until the window is available within the default timeout of 20 seconds, specified by the window wait built-in setting.
2. When the timeout is reached but the window is still unavailable, TestArchitect issues a Failed report.
3. With the check window not exists action:
1. If the specified window is available, TestArchitect waits until the window is unavailable within the default timeout 20 seconds, specified by the window wait built-in setting.
2. If the timeout is reached but the window is still available, TestArchitect issues a Failed report.