If the object on which you want to execute an action is not detected within the specified time-out, you can leverage generative AI based fallback to automate the specific dynamic webpages, decreasing the possibility of the Recorder action failure in the bot due to UI element changes or dynamic properties.
When text-based fallback triggers, Generative Recorder extracts the source code surrounding the target UI element's anchor text (preceding text), redacts and anonymizes business-sensitive data, and sends only the UI-element-specific code to the generative AI service. The model returns one or more candidate XPath values, which the system validates against the live page before applying. As an additional check, Generative Recorder verifies that the fallback DOMXPath corresponds to the correct element type, for example, if the action involves data entry, the system confirms the element is a text box and not a button or label.
GenAI text-based fallback provides resilient bot playback by dynamically recalculating element locators when primary or native selectors (such as XPath, DOM paths, or IDs) fail due to UI changes. It identifies web elements whose label text is split across multiple child elements, such as a link built from separate icon, name, and description spans. This improves automation self-healing and reduces playback failures in modern web applications without requiring you to recapture existing recordings.
- From the Bot editor, navigate to .
- In the , enable the Use Generative AI-based
fallback option.
- These are bot level settings. Hence, when you enable generative AI-based fallback, all the capture actions occurring in that specific bot will use these same settings with a time out of 30 seconds.
- Starting from Recorder package (version 3.1.5 and later), the Generative Recorder configuration settings will be visible regardless of whether a Recorder action is added in the Bot editor. To save the configuration settings, ensure that you use at least one action in your automation.
Automatically update DOMXpath values in the debug mode
To update these values at runtime, run your automations in Debug mode. You can choose to update your DOMXPath with the recommended value or to skip it. When you select the Stop automation option, the bot execution will be stopped.
When you update your DOMXPath with the recommended value, ensure that you deselect other invalid or dynamic properties in your search criteria before running your automations again. If these dynamic properties remain selected and are combined with the new DOMXPath, the Recorder fails and fallback is triggered again.
You can also move the fallback notification dialogue window at the desired location on the screen according to your needs and preferences thus improving the visibility of your business application and the fallback.
Capture using surrounding text
Generative Recorder captures and uses surrounding context information such as nearby labels, element position, container structure, and neighboring elements to identify UI elements more accurately during automation execution with GenAI text-based fallback. This improves automation resiliency for modern web applications where UI elements frequently change due to dynamic DOM updates, layout shifts, or attribute modifications.
Caching of successful Generative AI responses
The Generative AI calls made during successful Generative AI-based fallbacks are now cached in the system memory and the region-based service which are then reused for subsequent executions of the same automation. This reduces the time taken for subsequent executions of the same automation significantly thus improving performance.