- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors
Orchestrator user guide
Problem: Users do not receive configured alerts either in the user interface or via email when those alerts are configured for user groups with a SAML provisioning rule.
Solution: To resolve this issue, you can add affected users to the Administrators local group which allows them to receive alerts.
Adding users to the Administrators group grants them with elevated privileges. Endeavor to understand the implications of these privileges. Ensure users are conferred administrator rights responsibly, maintaining a balance between the need for alerts access and preserving system security.
The following table lists possible errors when starting jobs in Orchestrator.
| HTTP Status Code | Error Code | Message | Description |
|---|---|---|---|
409 | InvalidStartJobRobotIds | Couldn't find any user with unattended robot permissions in the current folder. |
There are no robots assigned to the current folders. Possible cause and solution:
Note: Users must be explicitly assigned to
folders; robots are not inherited from groups.
|
409 | InvalidStartJobRobotIds | Couldn't find the specified unattended user/robot in the current folder. |
The robots specified in the start jobs payload are no longer available in the folder. Verify that the job parameters are up to date with the users and robots available in the folders, then retry the job creation with the updated parameters. |
400 | InvalidArgument | Cannot set a specific priority value when a standard job priority setting is selected. |
The start jobs payload cannot have both
Priority and
SpecificJobPriority settings set.
Specify only one of these two properties in the payload. |
400 | InvalidArgument | A job cannot have both input file and input arguments. |
The start jobs payload cannot contain both
InputArguments and
InputFile.
Both options represent input arguments but in different formats. Only one option must be specified. |
400 | AttachmentNotFound | Attachment does not exist. |
The attachment specified in the
InputFile property
could not be found.
Verify that the file exists and the path is correct. |
404 | ItemNotFound | The job's associated process could not be found. |
The process you are trying to run does not exist or has been deleted. Ensure the process still exists in Orchestrator and has not been removed. |
409 | ParameterInvalid | Windows process. The selected connected machine can not run this process. |
The process you are trying to run is Windows-specific, but all connected machines are running on another OS. Make sure the current folder includes Windows machine templates with active Windows sessions. |
400 | InvalidReleaseKeyAndName | Undefined process. |
The process identified by the given process key
(
ReleaseKey) could not be found.
Check if the process still exists and confirm that the correct
ReleaseKey is used.
|
409 | UserDoesNotHaveRobot | Cannot find a personal robot configured. |
The job was started as Run as Myself, but there is no robot configured for the current user. Possible fixes:
|
409 | UserDoesNotHaveRobot | Foreground job requires an unattended robot to be defined on your user |
Foreground job requires an unattended robot to be defined for your user. Enable the unannteded robot for the user. |
409 | UnattendedRobotCredentialsNotFound | Foreground process requires you to have an unattended robot with credentials defined. |
The job was started as Run as Myself, but there is no robot configured for the current user. Possible fixes:
Note: For foreground automations to run
unattended, you must also provide Windows credentials when enabling
the Unattended Robot.
|
400 | ParameterInvalid | {license} runtime license selected. There are no {license} runtimes configured on the templates in this folder. |
Could not find any machine with the required runtime type in the folder. Check the machine templates assigned to the folder, and ensure the correct runtime slots are available according to the license. Example: For unattended jobs, make sure there is a template with unattended slots defined and a host connected to that machine template |
409 | NoMachineAssociatedWithFolder | Could not find a machine with Unattended or NonProduction runtimes in the current folder. |
The runtime type was not specified, and there is no template assigned to the folder that can execute this job. Review the machine–folder assignments and verify that the assigned machine templates have appropriate runtime slots. |
409 | InvalidArgument | Could not find the specified machine in the current folder. |
The machine template specified in the start jobs payload was not found in the current folder. Check the machine–folder assignments and confirm the machine template is correctly associated. |
409 | ParameterInvalid | Background process selected. This machine/template is configured for running foreground processes only. |
The selected process is configured to execute without opening an interactive session, but no machine supports Background automation in the current folder. Add or configure a machine template that allows Background automations. |
400 | ParameterInvalid | Robots without credentials cannot run processes that require an interactive session. |
The selected robots do not have Windows credentials configured, so an interactive session cannot be opened. Go to , select Custom Windows Credentials, and provide valid Windows login details. |
