Skip to end of banner
Go to start of banner

Atlassian CLI error handling

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Error handling

Care is taken to return the appropriate exit codes to the command processor. This makes it possible to do error handling in automation scripts. Error and error logging output is directed to standard error.

Error formatting macro: csv: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null

Error type, Exit code
Windows, Exit code
Other, Description
SUCCESS, 0, 0, Normal exit
CLIENT_EXCEPTION, -1, 255, "The client has found a problem with the request and is reporting an error with a message."
PARAMETER_PROBLEM, -2, 254, "The client processed the command parameters and found a syntax error or missing required parameters according to the [parameter definition]"
REMOTE_EXCEPTION, -3, 253, "The remote system has reported an error. The error message comes from the server."
FAILURE, -99, 157, "The client program failed in an unexpected way."

  • No labels