We initially installed a development agent on an AWS server to enable the execution of a Robotic Process Automation (RPA) process. When the AWS server is connected, the RPA process runs smoothly. However, when the AWS server gets disconnected, the agent goes offline, causing interruptions in the RPA process.
To address this issue, we attempted to use a task scheduler, which previously allowed us to activate the agent at scheduled times or manually. Unfortunately, the task scheduler has recently been unreliable, failing to activate the agent as expected. This problem has been occurring only in the development and testing AWS servers for the past month, while the production environment continues to function properly.
I discovered a beneficial feature called "Auto Sign-In" in Appian RPA, which offers the ability to automatically restart a bot without requiring manual login to AWS. This feature aims to provide a convenient and uninterrupted execution of the RPA bot.
However, it appears that the "Auto Sign-In" feature did not function as expected and did not successfully restart the bot.
It is crucial to resolve this problem promptly to ensure uninterrupted execution of the RPA process in the development and testing environments.
We kindly request your assistance in providing a solution to address the issue at hand, so that we can promptly work on implementing the recommended steps. We appreciate your assistance in advance.
Thanks & Regards,
Discussion posts and replies are publicly visible
Hi Nisha, could you open a support case so we can investigate why the automatic sign-in service isn't restarting your agent?
Hi Tien Bui I appreciate your response to my question.
While we have taken steps to address the auto sign-in issue through a ticket, our primary concern revolves around ensuring that the bots are deactivated upon disconnection from the AWS server, particularly for the dev agent. It is worth noting that even with the utilization of the "run as administrator" option and keeping the AWS open, the bot continues to function, but unfortunately, it goes offline once the connection is lost. Despite attempting the auto sign-in approach based on documentation, it has proven ineffective in resolving the issue.
To resolve the interruptions in the RPA process, we need to investigate the connectivity between the development and testing AWS servers and address any potential network issues. Thanks
Thank you for the response. In order to resolve these connectivity issues, could you please provide a detailed explanation of the steps involved? This will enable me to perform the necessary actions and effectively address the problem.
To resolve the connectivity issues between your development and testing AWS servers, review server status, validate security group rules, examine network ACLs, check VPC configurations, inspect routing configurations, test network connectivity, monitor system logs, enable logging in the RPA agent, and engage AWS support if needed.
Hope it will helps you.
We are actively progressing with the steps you recommended and will ensure to provide you with timely updates.
Hello Nisha, were you able to resolve your problem? I happen to be experiencing the same issue.
© 2023 Appian. All rights reserved.