How to invisible an Attended Job for not running on Unattended Robot?

Feedback Orchestrator
,
1

Hi,

I’ve encountered a recurring issue where a user manually run an attended job on an Unattended Robot via Orchestrator. This job includes a message box activity, which causes the robot to remain in a running state indefinitely since unatteded robots cannot interact with pop-up messages.

despite multiple reminders and training session, the user continues to repeat this mistake. Unfortunately, I don’t monitor job traffic 24/7, so if this happens and goes unnoticed, it cause cause other jobs to get stuck in a pending state. Eventually, this leads to timeouts and delays, which understandably frustrate other users.

let me know how you resolve the problem if you have case as me. I wish the OC has a feature to visible/invisible like “Hide process for Attended User”.

Orchestrator version 24.10.x

Regards,
Indra

2

@irahmat

I know this is frustrating

but as of now one way we followed is to have a different sub folder for attended automations and have not assigned any robot or unattended users

cheers