Common errors
The following are errors common to all API actions on the SC//Reliant™ platform. Errors that are returned by specific API actions are listed in the errors table for that action.
| Code | Message | Cause |
|---|---|---|
| 1 | Platform not specified | The SC//Reliant Virtual Controller (RVC) version installed on the node is incompatible with the API request. |
| 400 | Bad Request | The request was missing the required parameters or had the wrong required parameters values. |
| 401 | Unauthorized | Authentication failed. |
| 403 | Forbidden | The user doesn't have permissions to perform the requested action. |
| 404 | Not Found | The resource couldn't be found. |
| 405 | Invalid Request | The request couldn't be understood or had nonexistent values. |
| 406 | Invalid Accepted Header | The header on the script to access the API is invalid. |
| 422 | Unprocessable Entity | The request doesn't include all of the required parameters, or the parameters are invalid. This error is returned for any failed validation in SC//Reliant Platform Manager. |
| 429 | Too many requests | The maximum number of requests was reached. |
| 500 | Internal server error | A transient internal error. |
When making Remote Execution Jobs that use the SC//Reliant Virtual Controller, for example when using the Jobs APIs, the following error messages may be returned.
| Message | Cause |
|---|---|
Cannot perform this operation. The High Availability Cluster is disabled. | The node is not a member of a cluster and thus the action cannot be completed. Some actions, such as toggling maintenance mode can only be performed on clustered nodes. |
Node <node_name> not discovered by RJE broker | The Remote Job Execution (RJE) broker couldn't reach the node. The node may be offline, busy with a long-running operation, or in a node group whose Choria Domain doesn't match the domain the node uses. See Troubleshooting RVC jobs. |