Generative AI-based fallback
- Updated: 2024/04/25
Generative AI-based fallback
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.
- From the Bot editor, navigate to .
- In the Use Generative AI-based fallback option. , enable the
- 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.
- Ensure that you use at least one action in the bot to load the Recorder package specific settings.
Automatically update DOMXpath values in the Debug mode
Generative Recorder offers recommendations, to automatically update automations to make those more resilient. When you run your automations in Run or Debug mode, you will receive recommendations to automatically update the DOMXPath (UI element path) with the value used in successful fallback enabling to make your automations more resilient.
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.
When you run a parent bot, you will have an option to update the DOMXPath value whereas for the child bot, the update option is not available.