Options of killing Terminal session connected directly

Help Activities
, ,
1

In task manager in details tab the terminal session appears as the following:

The image displays the Windows Task Manager showing multiple instances of various UiPath processes currently running. (Captioned by AI)
The image displays the Windows Task Manager showing multiple instances of various UiPath processes currently running. (Captioned by AI)742×469 82.4 KB

while in the process tab it is of this way:

The image shows the Windows Task Manager displaying various running applications, including UiPath Executor, UiPath Studio, Notepad, Task Manager, Windows Command Processor, Windows Explorer, and Windows PowerShell. (Captioned by AI)
The image shows the Windows Task Manager displaying various running applications, including UiPath Executor, UiPath Studio, Notepad, Task Manager, Windows Command Processor, Windows Explorer, and Windows PowerShell. (Captioned by AI)721×664 51.4 KB

I don’t want to kill it via terminal session- close connection because of the following:

  1. Bot was built in lower version terminal package which was update to latest version 2.8.1.
  2. we started to notice that the bot was failing to load the login screen with following error:
    “Set Field at Position - Username”: Terminal error: ErrorWaitReady

Terminal Session error
Terminal Session error780×528 2.96 KB

I was thinking Hard kill could solve this problem
Could anyone help me out with this problem

2

Hi @quick_123,

Even i faced the same issue with terminal direct connection. Some times its opens multiple session in rare scenario.

I have done for each transaction checked wheather the session is already exists or not.

Finally i have done where ever using terminal connection used to close connection if any exception occured.

Regards,
Arivu

3

Hi @arivu96 , The screen is just blank in init state itself, is there a work around for this situation