Skip to main content
Question

Bot Launcher for user session USERNAME crashed.Last recorded command at line number XX.

  • July 16, 2025
  • 4 replies
  • 140 views

MAIYA_0
Navigator | Tier 3
Forum|alt.badge.img+5

I am encountering this error “Bot Launcher for user session USERNAME crashed.Last recorded command xyz at line number XX”.

 

 

Requesting your helps in resolving this?

4 replies

jshaji
Forum|alt.badge.img+5
  • Navigator | Tier 3
  • July 16, 2025

I am encountering this error “Bot Launcher for user session USERNAME crashed.Last recorded command xyz at line number XX”.

 

 

Requesting your helps in resolving this?

Try restarting the bot launcher in the task manager


Forum|alt.badge.img+4
  • Navigator | Tier 3
  • July 17, 2025

I am encountering this error “Bot Launcher for user session USERNAME crashed.Last recorded command xyz at line number XX”.

 

 

Requesting your helps in resolving this?

You can check error log details in below path also you can try restarting the Bot agent service and try to upgrade recorder package.

C:\ProgramData\AutomationAnywhere\BotRunner\Logs\Bot_Launcher_<username>.log

 

 


MAIYA_0
Navigator | Tier 3
Forum|alt.badge.img+5
  • Author
  • Navigator | Tier 3
  • July 17, 2025

I am encountering this error “Bot Launcher for user session USERNAME crashed.Last recorded command xyz at line number XX”.

 

 

Requesting your helps in resolving this?

Try restarting the bot launcher in the task manager

Tried this so many times, but stil same issues


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • July 17, 2025

Hi ​@MAIYA_0 ,

 

I have faced this issue in my recent Project with a customer where the resource usage was high during the crashes. One of their applications was heavily utilizing the CPU & Memory due to which the VM was getting disconnected during the Bot execution. In such case, the Bot launcher will get crashed for sure.

 

They identified the application and neutralized its usage in order to fix this problem. 

 

For your case, it will make more sense to you if you check the Event logs in the VM during the crashes to identify the root cause.

 

Hope this will help.