Unattended Robot Disconnected" Notifications for a Machine I Cannot Find

[Matias_Clemente.Arg (Matias Clemente)]

Hello everyone,

I’m trying to troubleshoot a persistent notification in my Orchestrator instance. I keep receiving “Unattended robot disconnected” and “Unresponsive” alerts for a machine named DESKTOP-BL3GA2D.

Here is an example of the notification:

Text

Unattended robot disconnected Unattended robot DESKTOP-BL3GA2D(DESKTOP-BL3GA2D\MATI) disconnected.

Following the alert, I went to the

Tenant > Machines

page to investigate, but I cannot find any machine object with the name DESKTOP-BL3GA2D in the list.

Here is a screenshot of my Machines page, which shows the machine is not there:

I’m confused as to why I’m receiving notifications for a machine that I can’t seem to locate in my Orchestrator setup.

Could anyone help me understand:

1. Where else could this machine

DESKTOP-BL3GA2D

be defined or referenced?

2. What could be causing these notifications if the machine object isn’t on the Machines page?

Any guidance on where to look next would be very helpful.

Thank you!

[nishiijain2000 (Nishi Jain)]

Hi @Matias_Clemente.Arg

This happens when a robot or user session still exists in Orchestrator, even though the machine object was removed.
Orchestrator does not monitor machines directly it monitors robot sessions.
If a robot was previously connected from DESKTOP-BL3GA2D and was never removed or disabled, Orchestrator continues to expect heartbeats and raises alerts when it does not receive them.

Try this

1 Go to Tenant → Robots
2 Search For DESKTOP-BL3GA2D or MATI
3 If found then Disable the robot OR Delete the robot
4 Save changes
It will stop the notifications

Thanks & Happy Automations

[arjun.shiroya]

Hie @Matias_Clemente.Arg ,

Those alerts are from an old unattended setup that still points to DESKTOP-BL3GA2D, even though the machine was removed.

Go to Tenant → Manage Access → each user → Unattended setup and delete or change any entry that uses DESKTOP-BL3GA2D\MATI.

Open Monitoring → Unattended sessions and delete any Disconnected/Unresponsive sessions for that machine.

Check your folder Triggers and make sure none of them targets DESKTOP-BL3GA2D
if yes, switch to a valid machine/template.

After cleaning these, the notifications for that machine will stop.

[Matias_Clemente.Arg (Matias Clemente)]

Thank you both for your responses (@arjun.shiroya, @arjun.shiroya); however, there is something I am not comprehending. I discovered that the machine DESKTOP-BL3GA2D is my current device. Therefore, it should not be deleted, especially since I am currently running some attended automations on it. Additionally, I could not locate where the association between DESKTOP-BL3GA2D and UiPath resides.

[arjun.shiroya]

@Matias_Clemente.Arg

No need to delete your machine! Alerts are from unattended setup (expects no login), but you’re using attended (your login)

Tenant > Manage Access > your user > Unattended setup → set to "No unattendedtemplate

Monitoring > Unattended sessions → delete disconnected ones for DESKTOP-BL3GA2D.

Folder Triggers → switch any unattended to attended/machine template.

Attended automations will keep working fine (no Machines entry needed)

[ashokkarale]

@Matias_Clemente.Arg

The screenshot shows you the machine templates. Open the machine template installed robots to see to which machine template your bot is connected to.

This is how you can from the Machine Template

From Monitoring page

[Matias_Clemente.Arg (Matias Clemente)]

Well, I have located what you indicated. If I delete any of the machines listed there, they would be removed entirely from the orchestrator’s map. I notice that I have some machines loaded that no longer exist. I would like to tidy up a bit and reorganize the licenses. Thank you for your assistance.

[ashokkarale]

@Matias_Clemente.Arg

You can remove the robots by clicking on the 3 dots at the end and select Remove

[Matias_Clemente.Arg (Matias Clemente)]

thanks for your response.