Recorder/DOMX failures on one Bot Runner in multi-user RDP environment

We have two unattended Bot Runner accounts running on the same Windows Server 2022 RDP multi-user machine, with separate Windows sessions and RDS CALs. Automation works normally under Bot Runner 1 but Recorder/DOMX browser interactions consistently fail under Bot Runner 2

Environment (identical for both accounts):

• OS: Windows Server 2022 Datacenter Azure Edition

• Chrome: 155.0.8059.40 (64-bit)

• Automation 360 Chrome extension: 4.5.0.0

• Extension ID: bboccnojhhoegfffpcllbeigipedjedf

• Both accounts use separate RDP sessions on the same machine.

Symptoms:

• Bots launch successfully and Chrome opens under both accounts.

• On Bot Runner 2, Recorder/DOMX consistently errors, saying it cannot find various elements but the error is often received after the element is successfully located and filled/clicked, but subsequently reports that the element cannot be found. Identical automation works normally under Bot Runner 1 on the same multi-user RDP server.

• Elements appear to flicker or be repeatedly re-evaluated before the action fails.

• Execution takes significantly longer on Bot Runner 2 than on Bot Runner 1.

Troubleshooting already completed:

• Restarted the server

• Uninstalled and reinstalled the Automation 360 Chrome extension under Bot Runner 2 without improvement.

• Confirmed both accounts have the same Chrome and extension versions. Neither has the legacy MV2 extension installed.

• Confirmed both accounts have active Automation.Bot.BrowserAgent.exe processes in their respective Windows sessions.