Skip to main content

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. 

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/

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?
 

 

Hello ​@SNorris ,

Were you able to resolve the issue? 

https://status.automationanywhere.digital/ is not specific to Dev/UAT/Prod but for all the Cloud tenant's statuses. 

The issue that you encountered is well documented in the KB article below. Please review it.

https://apeople.automationanywhere.com/s/article/When-running-a-bot-from-a-private-workspace-the-bot-fails-with-a-User-Cancelled-or-Forcefully-Closed-message-This-occurs-if-the-browser-tab-where-the-bot-was-initiated-is-closed-during-the-operation 

Reply


Terms & ConditionsCookie settings