AARI Co-Pilot Form No Longer Working

​@jane.neasham That’s very odd. An empty drop-down list box should still appear like this:

Does it appear the same way (gray text box) if you try another browser?

Are you displaying this Form from a Process or from a Task Bot using the Interactive Forms package?

Where is this drop-down getting the program listing from? Is the data source working properly?

I think I found the reason … it was unable to connect to the virtual machine. Once a connection was restored the box was visible.

However, I now have a new issue where unattended bots loose connection to the virtual machine. The unattended bot ran as scheduled correctly, but when a subsequent scheduled bot tried to connect to the same virtual machine using the same credentials, it is unable to log in, and the virtual machine locks the account. The log in credentials have been unchanged and are correct, as the first scheduled bot logged in with no issue.

This is the first time I have experienced an issue like this, and I can’t determine if its an issue with the Control Room set up, or an issue with the virtual machine. The unattended scheduled bots have been running for months with no issues until yesterday.

I managed to get it working … but I’ve identified the issue.

The bot was unable to connect to the virtual machine. We seem to have an issue where the virtual machine is locking after one run of a scheduled unattended bot. The scheduled bot will run, connect successfully to the virtual machine with the correct log in credentials. Then when subsequent scheduled bots run, they are unable to connect to the virtual machine, and the virtual machine account locks due to failed log in attempts.

I am unsure if this is an issue with the virtual machine, or the Control Room set up, although no changes have been made within the Control Room.  

I’ve not experience issues like this before, and the unattended scheduled bots have been running successfully on the virtual machine for a number of months