Skip to main content

Exit Codes

Automation should use the process exit code to decide whether a run succeeded, failed permanently, or should be retried.

Exit codeMeaningTypical handling
0Success, including runs with warnings.Continue. Review result CSV when needed.
1CLI error: configuration, authentication, mapping, or IO problem.Fix input, mapping, token, or paths before retrying.
2Validation error: at least one invalid row or response rows could not be matched.Review result CSV. This is usually a completed business result, not an infrastructure retry.
3Temporary error: timeout, rate limit, server error, or TEMP_ERROR.Retry later.
4Entitlement or quota exhausted.Check license or quota before retrying.

API Error Mapping

API conditionExit code
Connection timeout or connection error3
HTTP 4001
HTTP 401 or 4031
HTTP 4024
HTTP 4091
HTTP 4293
HTTP 500 or higher3

Result-Based Exit Codes

After a result CSV is written:

  • Any ERROR row returns exit code 2.
  • Any Unavailable or TEMP_ERROR row returns exit code 3 when there are no stronger errors.
  • Otherwise the command returns 0.

Folder mode returns the worst exit code from all files processed in that run.