Skip to main content
Question

Sub bot is not able to recognize the chrome window when it is run through the master BOT

  • December 31, 2025
  • 3 replies
  • 18 views

Forum|alt.badge.img+4

We have a sub-bot that performs tasks on a Chrome page but it has suddenly stopped working on the Chrome page.

When we run the sub-bot individually it triggers successfully and completes the task. However when it is triggered through the master bot as part of the workflow it fails at the same step. We also created a new sub-bot with the same workflow but it faces the same issue.

 

AAChromeBotBrowserAgent.log: 
2025-12-24 12:18:44,099 [(null)] THOMASCOOK\RPA.Client6 [5] INFO BrowserAgent -  > Sending message to the active named pipe client.
2025-12-24 12:18:44,100 [(null)] THOMASCOOK\RPA.Client6 [5] INFO BrowserAgent -  > Message sent to the active named pipe client.
2025-12-24 12:18:44,102 [(null)] THOMASCOOK\RPA.Client6 [5] INFO BrowserAgent -  > Message not sent to client as activeNamedPipe is not connected.
2025-12-24 12:18:44,103 [(null)] THOMASCOOK\RPA.Client6 [5] INFO BrowserAgent - BrowserCommunicator:StartReader > Waiting for message from browser.
2025-12-24 12:18:44,104 [(null)] THOMASCOOK\RPA.Client6 [5] INFO BrowserAgent - ConsoleReaderWriterAsync:ReadAsync > Reading Length of message.
2025-12-24 12:18:51,144 [(null)] THOMASCOOK\RPA.Client6 [5] ERROR BrowserAgent - BrowserCommunicator:StartReader > No Data Received. The chrome browser might be closing.End of the stream.
2025-12-24 12:18:52,885 [(null)] THOMASCOOK\RPA.Client6 [5] ERROR BrowserAgent - BrowserCommunicator:StartReader > No Data Received. The chrome browser might be closing.End of the stream.

Bot_Launcher.log: 
2025-Dec-24 Wed 12:18:14.195 ERROR [BotRunner-45f15124-9b09-4f59-b7f6-65a6e0c3e5d5_35ac9091496fe618] - com.automationanywhere.webbrowser.adapter.ChromiumBrowserAdapter {deploymentId=45f15124-9b09-4f59-b7f6-65a6e0c3e5d5_35ac9091496fe618, traceId=35ac9091496fe618} - executeBrowserRequest(ChromiumBrowserAdapter.java:357) - Error occurred while executing Chrome browser request. Retrying... java.util.concurrent.ExecutionException: java.lang.IllegalStateException: SetNamedPipeHandleState failed with HRESULT= 232-2147024664
    at java.util.concurrent.CompletableFuture.reportGet(Unknown Source) ~[?:?]
    at java.util.concurrent.CompletableFuture.get(Unknown Source) ~[?:?]
    at com.automationanywhere.webbrowser.adapter.ChromiumBrowserAdapter.executeBrowserRequest(ChromiumBrowserAdapter.java:328) ~[bot-launcher.jar:?]
    at com.automationanywhere.webbrowser.adapter.ChromiumBrowserAdapter.findTab(ChromiumBrowserAdapter.java:102) ~[bot-launcher.jar:?]
    at com.automationanywhere.webbrowser.adapter.ChromeBrowserAdapter.findTab(ChromeBrowserAdapter.java:14) ~[bot-launcher.jar:?]

3 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • December 31, 2025

@Samadhan Almost seems like the plug in has a communication pipe open with the master bot and doesn't want to open a second one for the child bot. If you're passing BROWSER variables to the child, that could be exactly what is happening. 


Forum|alt.badge.img+4
  • Author
  • Cadet | Tier 2
  • December 31, 2025

@Aaron.Gleason I am not opening or using any browser in the master bot. All browser related activities are handled exclusively within the sub bot. The sub bot opens and manages its own browser instance and uses its own browser variables no browser variables or handles are passed from the master bot to the sub bot.


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • December 31, 2025

@Samadhan Doesn’t happen often, but I’m stumped. There is no reason that shouldn’t work that I know about. I’ll leave this open for others to comment.