This issue happens to an on-prem control room and while the task bot stuck on this status, the coming task bot will stay queued for ever so at the end, I have an infinite queue.
Process is stuck in 'Pending Execution' status after completing whole task bot

Best answer by ravi.pothana
Hi
After analyzing the logs, I identified the below error in the log files.
User - cloudsigma has attested the device credentials, but not chosen to reuse an existing session. Please select the auto login setting as use existing session
Unable to process bot command successfully java.lang.RuntimeException: Timed out waiting for user rdp session to be available.
when the "Attest Device Credentials" option is enabled for a specific runner user ID, the corresponding runner user must maintain an active and unlocked user session to execute the bot. If an attempt is made to run the bot in an unattended session, the process will fail and generate an error due to the lack of active user authentication.
You can perform the steps below:
1. Login to the Control Room using Admin account.
2. Click on Administration > Select Users
3. Select the user with which the bot is running
4. Uncheck the Attest Device Credentials checkbox and then run the bot in unattended mode.
* You may have to re-type username and password on the bot runner.
------------
OR
Set the autologin to choose "Reuse an existing session"
https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/administration/settings/cr-auto-login-settings.html
Note: When you use the Reuse an existing session option, ensure user sessions are available. If there is no existing user session, triggers and bot deployments will fail.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.