Fallback Window Appears Even When Valid DOMXPath Is Used (Community Edition)

Hi Team,

I am facing an issue in Automation Anywhere Community Edition related to the Fallback Window.

Even when I use a valid and capturable DOMXPath for an object, Automation Anywhere still triggers the Fallback Window during bot execution. Because of this, the bot execution gets interrupted and automation stops.

I have already confirmed that:

• The object is properly captured

• The DOMXPath is stable and correct

• The application is visible and accessible during runtime

Despite this, Automation Anywhere continues to open the fallback window.

My Questions:

1. Is there any way to disable, suppress, or remove the fallback window in the Community Edition?

2. Are there any best practices or alternative approaches to avoid fallback window invocation when DOMXPath is working correctly?

3. Is this a known limitation of the Community Edition?

Any guidance or workaround would be greatly appreciated.

Thank you in advance for your support.