Skip to main content
This page contains all error codes that can occur in the Intuned system. For operational reasons and cancellation codes, see reason codes.

​
Error Structure

All errors in the Intuned system follow a standardized structure with the following fields:
  • code - Stable, machine-readable error identifier
  • category - Broad classification for retry/alert rules
  • message - Human-readable description of the error
  • retriable - Boolean indicating if the operation can be retried
  • doc_url - Optional link to documentation for this error
  • correlation_id - Optional ID for tracing the error in logs
  • details - Optional additional context specific to the error

​
Error Categories

​
infrastructure

Internal system errors within the Intuned platform infrastructure. These are typically retriable and indicate temporary issues with the service.

​
execution

Errors that occur during script or automation execution.

​
auth

Authentication and authorization related errors. For more information about auth sessions, see the auth sessions overview.

​
user

Errors caused by invalid user input or client-side issues. These are typically not retriable without correcting the input.

​
billing

Billing and credit-related errors that prevent operations from proceeding due to account limitations. For more information about pricing and credits, see our pricing page.

​
Script Execution Error Codes

​
script-execution-exception

An error occurred while running the browser automation script. this usually happen when the automation throw an un-handled exception.

​
script-no-valid-output-received

The browser automation finished, but no valid output was received from the script. This happens if the result should be in a specific format, but the automation returned an invalid output.t

​
script-timeout

The browser automation request exceeded the specified timeout limit in the request/project.

​
script-unexpected-error

Unexpected error when communicating with the script; there are multiple reasons for this error. The most popular one is capacity issues, such as insufficient memory to run the script, or CPU throttling that might cause possible issues when initializing the browser or communicating with the automation script.

​
script-process-crashed

The runtime process has crashed, usually due to OOM or critical server issues, or new app deployment during a run execution.

​
Auth Session Error Codes

For more details about working with auth sessions, see developing auth sessions and consuming auth sessions.

​
auth-check-failed

The auth session check script returned false, indicating invalid or expired credentials.

​
check-attempts-failed

All auth session check attempts have failed for the run.

​
create-attempts-failed

All auth session creation attempts have failed for the run.

​
post-create-check-attempts-failed

All post-creation authentication check attempts have failed for the run.

​
auth-session-not-ready

The authentication session is not ready for use. this happens when auth session status is expired/pending and you try to use it in a run that has auto-recreate set to false.

​
auth-session-already-in-use

The authentication session is currently being used by another operation.

​
Run Execution Error Codes

For more information about monitoring runs, see how to monitor runs.

​
api-attempts-failed

All API execution attempts have failed for the run.

​
Client API Error Codes

​
bad-request

The request was malformed or contained invalid parameters.

​
unauthorized

Authentication credentials are missing or invalid.

​
forbidden

Access denied due to insufficient permissions.

​
not-found

The requested resource could not be found.

​
method-not-allowed

The HTTP method is not supported for this endpoint.

​
request-timeout

The request took too long to process and timed out.

​
conflict

The request conflicts with the current state of the resource.

​
unprocessable-entity

The request was well-formed but contains semantic errors.

​
sunsetted-route

The API route has been deprecated and is no longer available.

​
insufficient-credits

Insufficient credits available to perform the requested operation.

​
insufficient-resource-credits

Insufficient resource-specific credits available for the operation.

​
workspace-invalid-billing-state

The workspace billing state prevents the operation from proceeding.

​
insufficient-resource-credits

Insufficient resource credits to execute the job run.

​
Server Error Codes

​
not-implemented

The requested functionality is not yet implemented.

​
internal-server-error

General internal server error that occurred within the system infrastructure. This error code rarely happens and if it does occur, it comes with a correlation_id and event details that you can share with Intuned support to resolve any issue you face.