Exit Codes
Automation should use the process exit code to decide whether a run succeeded, failed permanently, or should be retried.
| Exit code | Meaning | Typical handling |
|---|---|---|
0 | Success, including runs with warnings. | Continue. Review result CSV when needed. |
1 | CLI error: configuration, authentication, mapping, or IO problem. | Fix input, mapping, token, or paths before retrying. |
2 | Validation 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. |
3 | Temporary error: timeout, rate limit, server error, or TEMP_ERROR. | Retry later. |
4 | Entitlement or quota exhausted. | Check license or quota before retrying. |
API Error Mapping
| API condition | Exit code |
|---|---|
| Connection timeout or connection error | 3 |
| HTTP 400 | 1 |
| HTTP 401 or 403 | 1 |
| HTTP 402 | 4 |
| HTTP 409 | 1 |
| HTTP 429 | 3 |
| HTTP 500 or higher | 3 |
Result-Based Exit Codes
After a result CSV is written:
- Any
ERRORrow returns exit code2. - Any
UnavailableorTEMP_ERRORrow returns exit code3when there are no stronger errors. - Otherwise the command returns
0.
Folder mode returns the worst exit code from all files processed in that run.