Understand exit codes for error handling in ACLI
ACLI takes care to return meaningful exit codes to the command processor. These codes make it easier to handle errors in automation scripts and CI/CD pipelines.
By default:
Standard output receives regular messages.
Standard error receives detailed error logs.
You can use the exit codes to programmatically respond to different types of errors.
Exit code reference
The following table describes the exit codes returned by ACLI. These codes can differ slightly between Windows and other operating systems.
Code Name | Exit Code (Windows) | Exit Code (Others) | Description |
|---|---|---|---|
|
|
| The command completed successfully. |
|
|
| The client encountered a problem with the request and returned an error message. |
|
|
| The client found a syntax error or missing required parameters. A help request also returns this code. |
|
|
| The remote system returned an error. The message comes from the server. |
|
|
| The client detected a condition that requires a unique error classification. Examples: The |
|
|
| The client encountered a database-related error while executing an SQL request. |
|
|
| The client failed in an unexpected way. Consider opening a support ticket. |