# Implementation of Timeout in GUI: Web Element Condition

**URL:** <https://community.automationedge.com/t/implementation-of-timeout-in-gui-web-element-condition/16812>\
**Category:** New Feature Ideas\
**Created:** [February 27, 2025, 1:50pm UTC](https://community.automationedge.com/t/implementation-of-timeout-in-gui-web-element-condition/16812 "2025-02-27T13:50:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnCosta](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@JohnCosta](https://community.automationedge.com/u/JohnCosta)\
**Post date:** [February 27, 2025, 1:50pm UTC](https://community.automationedge.com/t/implementation-of-timeout-in-gui-web-element-condition/16812/1 "2025-02-27T13:50:01Z")

</div>

In some cases, I need to validate whether an element is present, and I usually use **GUI: Web Wait Until**. However, when using a loop, it does not allow the error hop to be a copy but rather a distribution, which does not meet the required needs.

As a workaround, I use **Web Element Condition** to check whether the element is present or not. However, when the element is not present, I have to wait for 30 seconds, which is the default timeout for the step. If there were an option to set the timeout, similar to **GUI: Web Wait Until** , this process would take significantly less time. Currently, a process that should take 20 seconds is taking 50 seconds due to this long timeout.