Skip to main content
Solved

Not able to run the BOT unattended

  • September 1, 2025
  • 8 replies
  • 58 views
A
Forum|alt.badge.img+3

Hi All,

 

We are not able to run the bots unattended for some reason, it was working fine but recently we are not able to run the bots unattended. Deployments are getting failed with below message -

 

com.automationanywhere.nodemanager.exception.UserLoginException: {"message":"User not logged into the machine.","details":"This may be due to multiple reasons.\n\n1. Check that your username and domain name is correct in the provided device login credentials.\n2. Login into the machine as that user before running the bot.\n3. Some other user may have logged into the machine.\n\n\n\nIf you continue to see this message, please contact your system administrator.","correctiveAction":"","code":"user.not.logged.in"}

 

 

Can you please help me, what could be the possible way to resolve this?

 

Thanks,

Akash

Best answer by AkashMalapur

We found the solution for this. Actually, there was another login entry has been logged in the AA DB/ global cache.

We followed below steps -

  1. We uninstall the Automation Anywhere bot agent from the control panel
  2. We stopped the Automation anywhere services if any running still
  3. We renamed the Automation Anywhere folders from Program files and Program data of C drive. Need to rename if available in user profile 
  4. We deleted the device from the AA control room 
  5. We reinstalled the Automation Anywhere bot agent and connected the Agent to the device
  6. We restarted the VDI machine, this is the main step… we need to restart the machine not signed out
  7. We were able to deploy the bots now in unattended mode

8 replies

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

Hi ​@AkashMalapur,

 

This error can happen due to multiple reasons. The most common cause for this issue is because of wrong deployment settings; it is important to set the correct deployment type to either RDP or Regular.

 

 

Please refer to the below article and see if any of the fixes are working for you or not.

 

Unable to run bots. Error: "User not logged into the machine" or "Unable to perform auto-login for user xxxx"

 

 

Padmakumar
A
Forum|alt.badge.img+3
  • AkashMalapur
  • Author
  • Cadet | Tier 2
  • September 1, 2025

Our deployment type is set to Regular only. 

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

Our deployment type is set to Regular only. 

Is your bot runner a remote machine? Then you should select RDP instead of Regular.

Padmakumar
A
Forum|alt.badge.img+3
  • AkashMalapur
  • Author
  • Cadet | Tier 2
  • September 8, 2025

​@Padmakumar  All our Devices are regular since day 1. and all are getting deployed and running in production smoothly but only this particular device is having issue… which according to my knowledge has the same settings as all the other devices 

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

​@Padmakumar  All our Devices are regular since day 1. and all are getting deployed and running in production smoothly but only this particular device is having issue… which according to my knowledge has the same settings as all the other devices 

 

Ok, In that case, please check the Device credential mapped for your Runner account. 

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

​@Padmakumar  All our Devices are regular since day 1. and all are getting deployed and running in production smoothly but only this particular device is having issue… which according to my knowledge has the same settings as all the other devices 

If that is the case, then it is highly likely caused by the incorrectness or unavailability of the device credential mapped with your Bot runner account.

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

​@Padmakumar  All our Devices are regular since day 1. and all are getting deployed and running in production smoothly but only this particular device is having issue… which according to my knowledge has the same settings as all the other devices 

Did you check the credential mapped for the runner account?

Padmakumar
A
Forum|alt.badge.img+3
  • AkashMalapur
  • Author
  • Cadet | Tier 2
  • Answer
  • September 17, 2025

We found the solution for this. Actually, there was another login entry has been logged in the AA DB/ global cache.

We followed below steps -

  1. We uninstall the Automation Anywhere bot agent from the control panel
  2. We stopped the Automation anywhere services if any running still
  3. We renamed the Automation Anywhere folders from Program files and Program data of C drive. Need to rename if available in user profile 
  4. We deleted the device from the AA control room 
  5. We reinstalled the Automation Anywhere bot agent and connected the Agent to the device
  6. We restarted the VDI machine, this is the main step… we need to restart the machine not signed out
  7. We were able to deploy the bots now in unattended mode
Terms & ConditionsCookie settingsAccessibility statement