"Hello everyone! I'm currently working with an RPA agent and I'm wondering if anyone has experience or insights on how to automatically start an RPA agent when the system restarts. I'd like to ensure that the agent is up and running without any manual intervention after a system reboot.
NOTE: We have a dedicated server for production where we store all our agents and files logs. However, we are experiencing scheduled server downtime every day. Fortunately, the server eventually comes back online, and we expect our bots to automatically go online without requiring any manual intervention. This ensures the continuous operation of our bots once the server is back up.Here are a couple of approaches I follow: 1. I have created a task scheduler using a bat.file, which allows me to automate the startup of the RPA agent at a specific time or during system boot.--- but unfortunately, the scheduled task isn't working as intended. It fails to activate the RPA agent when it's supposed to, even during system restarts. 2. I also copied and pasted the necessary RPA files into the system's startup folder. This ensures that the RPA agent is automatically launched when the system starts up.---- I tried using the startup folder to trigger the RPA agent, but unfortunately, it didn't work as expected. The agent icon appears in grey color sometimes there is no icon appears indicating that it is not functioning properly.3.I came across a useful feature called "Auto Sign-In" in Appian RPA. With the help of this feature, we can automatically restart a bot without the need to log into AWS. It provides a convenient way to ensure the seamless execution of the RPA bot.----- but this didn't work as expected. These approaches have been testing automating the startup process of the RPA agent.Any suggestions, tips, or best practices would be greatly appreciated. Thank you!"
Discussion posts and replies are publicly visible
#3 should have addressed your issue. Can you provide more details on why it didn't work as expected? What was the error?
I have configured auto sign in in dev region and tried to restart my aws server and the agent didn't got active upon restart. due to this i am unable to run rpa as the agent is not active There was no error but i was expecting that after configuring auto sign in when i restart, the agents will be online and i will be able to execute RPA with out singing into AWS servers.I have followed this documentation : https://docs.appian.com/suite/help/23.2/rpa-9.2/robots.htmlI have attached screenshot for reference.please let me know how to proceed further.
It seems like you're "signed in". Did you manually click the sign-in button on this page prior to your AWS server re-starting? If so, you should do the following:
1) Click sign out here. Your robot should therefore by in STANDBY status afterwards.
2) Restart your aws server. Your robot should remain in STANDBY status.
3) Once you execute a robotic task, the sign-in service will log in as needed, bringing your agent ONLINE to perform the tasks. When the task completes and there's no more tasks queued up for that robot, then your agent will go back to STANDBY status.
1. Just to clarify i need to click sign out as i already signed in 2. restart my server then auto sign in will login automatically and it will perform the task NOTE: As i already using auto sign in to open the session in a particular resolution ie : 1366 x 768 As you said to sign out and perform the restart ---open the session in a particular resolution this won't effect the performance right ?
Correct. That resolution dropdown means that every time the process tries to sign in (when you run a robotic task), it's going to sign in first with that resolution selected on that robot.
Thanks Tien BuiI will try the approach you suggested and i will update you.
Hi Tien Bui,I have tried the approach but it didn't activate the agent due to that the rpa process didn't move further it was waiting for the resource.1. I have make sure not to manually click the sign-in button on this page2. Then i have done a restart of the server 3. Tried to run a rpa process but its was stuck here 4. After waiting too long this happens 5. The status of the agent is also change from online to Disabled 6. The auto sign in is logging successful Messages in execution log :[INFO] 2023-07-07 05:50:21 - - Successfully signed into the user session on HR-Billing-Resource.7. but its not activating the agent Messages in execution log : [INFO] 2023-07-07 05:50:21 - - Waiting for the RPA agent to be up and runningPlease let me know how to proceed further or missing anything i will work on that.