Skip to main content
Cadet | Tier 2
June 10, 2025
Solved

bot unable to stop the bot in CR

  • June 10, 2025
  • 2 replies
  • 122 views

 

    Best answer by Aaron.Gleason

    Try this page I made to reset or remove the device:

    https://developer.automationanywhere.com/deletedevice.php 

    2 replies

    Aaron.Gleason
    Automation Anywhere Team
    Automation Anywhere Team
    June 10, 2025

    Try this page I made to reset or remove the device:

    https://developer.automationanywhere.com/deletedevice.php 

    Tamil Arasu10
    Most Valuable Pathfinder
    Most Valuable Pathfinder
    June 11, 2025

    Hi ​@balu567 

     

    Steps to Resolve "Unknown" Bot Status

    1. Check Device Availability:

      • Go to Devices in the Control Room.
      • Ensure the device is connected and active.
      • If it's part of a device pool, make sure it's not overloaded or misconfigured.
    2. Stop the Bot from Control Room:

      • Navigate to Activity > In Progress.
      • Locate the bot with "Unknown" status.
      • Click Stop or Move to History (if Stop is disabled) to clear the stuck instance 
        .
    3. Restart Bot Agent Service:

      • On the machine where the bot is running, restart the Automation Anywhere Bot Agent service.
      • This often re-establishes the connection and updates the bot status.
    4. Clear Device Lock:

      • If the device is locked due to a stuck bot, you may need to:
        • Unregister and re-register the device.
        • Or use the API to reset the device (available in Enterprise edition).
    5. Check Logs:

      • Review logs in:
        • Node-manager
        • WebCR_Devices
        • Control Room Audit Logs
      • These can help identify if the issue is due to a script error, device timeout, or network issue.
    6. Create a New Bot (Workaround):

      • If the bot remains stuck and cannot be stopped, create a new bot, copy the logic, and run it separately
    _Tamil_