Orchestrator and Robot Management
Structure and objects
Orchestrator organises everything under a tenant, then into folders (modern folders) that hold processes, queues, assets and the users/robots with access. Roles grant permissions; a robot identity is bound to a machine and a licence type (Attended, Unattended, Studio, StudioX, Testing). A process is a published package version mapped to a folder; a job is one execution; a trigger starts jobs on a schedule or when a queue item is added.
Queues decouple producers from consumers. Items carry a unique reference, priority, deadline and retry settings. Statuses are New, In Progress, Retried, Successful, Failed and Abandoned (the robot died mid-transaction). Assets hold environment-specific values as Text, Bool, Integer, Credential or Windows Credential, scoped to a folder; a credential asset returns username and password separately. Storage buckets hold files, Action Center holds human tasks, and audit logs record configuration changes.
Traps
- Mixing classic environments with modern folders in the same answer.
- Assuming an asset defined in one folder is visible in another.
- Forgetting that the unique reference can cause Add Queue Item to reject a duplicate.
- Confusing Failed with Abandoned, or Retried with In Progress.
- Overlooking that an unattended job also requires a machine template and unattended runtime licence.
Rule of thumb
For anything that must run headless on a schedule, verify four things: unattended licence, machine template, folder access, and the process published at the right version.