How to handle if any field is missing on the webpage?

Get Help & Discuss Process Studio
1

Help me in this

4

In AutomationEdge Process Studio, when an expected field or element might be missing from a webpage (for instance, optional form fields, conditional pop-ups, or dynamic UI elements), you can handle it using the following approaches:

1. Pre-Check Field Existence using GUI: Web Element Condition (Recommended)

Before attempting to interact with the field (such as clicking or entering text), check whether the element exists on the page:

  • Add Step: Insert a GUI: Web Element Condition step12.
  • Configure Condition: Set Condition to Is displayed34.
  • Output Field: The step outputs a Boolean result (True if the element is present, False if missing) into an output field (e.g., Output)56.
  • Branch Logic: Connect a Filter Rows or Switch / Case step downstream to evaluate the Boolean output:
    • If True $\rightarrow$ Route to steps that enter data or read the field.
    • If False $\rightarrow$ Bypass the field and continue execution without causing an error.

2. Configure “Do Not Fail” / “Fail If Error Occurs = No” & Default Values

If you are using steps like Web Get Value or Web Set Value and want the workflow to continue smoothly even if a field is absent:

  • Disable Failure on Error: Set Fail If Error Occurs to No (or select Do Not Fail) in the step configuration78.
  • Set Default Value: Configure Default Value If Failed79. If the field is missing on the webpage, Process Studio assigns this default value (e.g., an empty string or default text) to the stream field and continues executing without halting the workflow79.

3. Use Step Error Handling Hops

You can handle missing element exceptions at runtime using Process Studio’s error-handling mechanism:

  • Right-click the Web GUI step (e.g., Web Set Value or Web Click) and select Error Handling to create an error hop (red arrow) to a secondary step10.
  • If the field is missing and the step throws a locator/timeout exception, execution automatically routes along the error hop to a fallback branch (such as logging the missing field or continuing to the next field)10.

4. Combine Web Wait Until with Timeout Control

If a field takes time to render or might not load at all:

  • Use a GUI: Web Wait Until step1112.
  • Set Expected Condition to Element visible or Element present1213.
  • Set a short Timeout (in Milliseconds)1314. If the element does not appear within the timeout, combine it with an error handling hop or Web Element Condition to safely skip it10more_horiz