# Surface Automation

**URL:** <https://community.automationedge.com/t/surface-automation/17594>\
**Category:** Process Studio\
**Tags:** rpa\
**Created:** [February 13, 2026, 12:43pm UTC](https://community.automationedge.com/t/surface-automation/17594 "2026-02-13T12:43:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohanb](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rohanb](https://community.automationedge.com/u/rohanb)\
**Post date:** [February 13, 2026, 12:43pm UTC](https://community.automationedge.com/t/surface-automation/17594/1 "2026-02-13T12:43:54Z")

</div>

While using the **Web Automation plugin** , sometimes the Web Element condition fails even though the element is visible on the screen.

What is the recommended way to handle dynamic web elements in Process Studio?

---

<div class="post-metadata">

**Author:** ![AETrainings](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@AETrainings](https://community.automationedge.com/u/AETrainings)\
**Post date:** [February 27, 2026, 12:54pm UTC](https://community.automationedge.com/t/surface-automation/17594/2 "2026-02-27T12:54:08Z")

</div>

Recommended way is to use dynamic X-path to locate the element.