How to resolve a #1666 error thrown when attempting to delete a user/machine from Orchestrator?
Issue Description:
Sometimes, when attempting to delete a user or machine within Orchestrator (Under 'Manage Access' tab), errors like these are observed:
- "This Robot has pending or running jobs and cannot be deleted. (#1666)."
- "The machine has running jobs in the specified folder(s). (#1666)"
This issue occurs when a process associated with the user/machine in a specific folder has either stalled in a pending state or is in an ongoing execution phase.
Resolution:
To resolve this, follow these steps:
- Visit each folder's "Jobs" page.
- Apply a filter to display the records in 'Pending State' and 'Running State'.
- Identify all the pending, running, or suspended jobs associated with the user/machine across all the folders they have access to, and systematically halt these jobs.
- Also, ensure the user/machine isn't linked to any active Triggers. If such a link exists, it's advisable to either detach the user/machine from these triggers or deactivate the triggers entirely.
- Once all ongoing or pending jobs are halted, and the user/machine is disassociated from any active triggers, proceed to delete the user/machine from the 'Manage Access' and/or 'Machines' page.
Performing these steps should relieve the user's account and machine from all current tasks, allowing for their deletion.