Skip to main content
Question

DEV Control Room Issues

S
Forum|alt.badge.img+1

Is anyone else experiencing issues in Dev control room when developing and/or testing bots?

I launch a bot to run and keep getting error saying;
 

“Forcefully closed the bot execution due to user stopping it.” 

And I’m not the one stopping the bot. Naturally there’s no more information than that. 

ALSO, does anyone know if AA has a link to a page where we can check the status of their cloud services?? It seems there was a maintenance performed on 3/6/2025 for US West and I thought it would be nice if they had a place where you could go to review real time status. 

    K
    1 person likes this
    • K
      komal.jadhav

    2 replies

    Aaron.Gleason
    Automation Anywhere Team
    Forum|alt.badge.img+10
    • Aaron.Gleason
    • Automation Anywhere Team
    • 504 replies
    • March 7, 2025

    Hi ​@SNorris -- that’s an interesting issue. First thing I would check is the Bot Runner logs on your development machine. (I’m assuming you’re testing the bot on a dev machine or VM.) Those logs are located in C:\ProgramData\AutomationAnywhere\BotRunner\Logs by default. Maybe they have more information regarding the issue.

    We do have a real-time cloud status page here:   https://status.automationanywhere.digital/

    Marc Mueller
    Vatsy
    Dineshkumar Muthu
    5 people like this
    • Marc Mueller
      Marc Mueller
    • Vatsy
      Vatsy
    • Dineshkumar Muthu
      Dineshkumar Muthu
    • Lu.Hunnicutt
      Lu.Hunnicutt
    • Shreya.Kumar
      Shreya.Kumar
    S
    Forum|alt.badge.img+1
    • SNorris
    • Author
    • Cadet | Tier 2
    • 3 replies
    • March 17, 2025

    The logs state the same thing; forefully closed.

    I checked the status page in the link provided and all are saying up and running.

    Now bots won’t run at all. They launch and start to run and since we wrap the entire bot in a Try/Catch, the very first thing it hits is the Catch with the error line number but no description. When I look at the log, says the same thing as it has said all along… Forcefully closed
    The bot is not being forcefully closed. it’s not running

    Is the link you provided for PROD Control rooms only? Or does it include DEV Control rooms?
     

     

    Reply


    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings