Exit Codes
The CLI uses semantic exit codes so scripts, CI pipelines, and AI agents can react to failure categories without parsing stderr.
Exit Code Ranges
Section titled “Exit Code Ranges”| Range | Category | Description |
|---|---|---|
| 0 | Success | Command completed successfully |
| 1 | General | Unexpected or unclassified error |
| 10–19 | Auth | Authentication and authorization failures |
| 20–29 | Input | Configuration, validation, and resolution errors |
| 30–39 | API | Sentry API and network errors |
| 40–49 | Feature | Feature availability and billing issues |
| 50–59 | Operations | Upgrade and OAuth flow errors |
| 60–69 | Command | Command-specific non-standard exits |
Complete Reference
Section titled “Complete Reference”| Code | Name | Description |
|---|---|---|
| 0 | Success | Command completed successfully |
| 1 | General Error | Unexpected error or unclassified failure |
| 10 | Not Authenticated | No credentials found — run sentry auth login |
| 11 | Token Expired | Auth token expired — re-authenticate |
| 12 | Token Invalid | Auth token rejected by the server |
| 13 | Host Scope | Request blocked — credentials don't match the target host |
| 20 | Config Error | Configuration or DSN problem |
| 21 | Validation Error | Invalid input found while the command runs (malformed ID, unknown value, etc.) |
| 22 | Missing Context | Required context (org, project) could not be determined |
| 23 | Not Found | A user-provided identifier could not be resolved |
| 30 | API Error | Sentry API returned an error response |
| 31 | Timeout | Operation exceeded its time limit |
| 32 | Rate Limited | Sentry API rate limit hit and the CLI could not wait it out — wait for the time in the error message, then retry with fewer parallel requests |
| 40 | Seer Not Enabled | Seer is not enabled for the organization |
| 41 | Seer No Budget | Seer requires a paid plan |
| 42 | AI Disabled | AI features disabled by organization admin |
| 43 | Seer Out Of Credits | Organization is out of Seer credits or hit its daily Seer spend limit |
| 44 | Seer Setup Required | Seer needs a GitHub or GitLab integration, or repositories connected to the project |
| 50 | Upgrade Error | CLI upgrade operation failed |
| 51 | Device Flow Error | OAuth device authorization flow failed |
| 60 | Output Error | Command produced output but the operation failed |
| 64 | Verify Failed | sentry local run --verify received no events from the SDK |
| 252 | Invalid Argument | An argument could not be parsed — see Argument errors |
Scripting Examples
Section titled “Scripting Examples”sentry issue list my-org/code=$?
case $code in 0) echo "Success" ;; 1?) echo "Auth problem (code $code) — run: sentry auth login" ;; 2?) echo "Input/config problem (code $code)" ;; 3?) echo "API/network error (code $code)" ;; 4?) echo "Feature not available (code $code)" ;; *) echo "Failed with exit code $code" ;;esacPython
Section titled “Python”import subprocess
result = subprocess.run(["sentry", "issue", "list", "my-org/"], capture_output=True)
if result.returncode == 0: print("Success")elif 10 <= result.returncode <= 19: print("Auth error — run: sentry auth login")elif 20 <= result.returncode <= 29: print("Input/config error")elif 30 <= result.returncode <= 39: print("API/network error")elif 40 <= result.returncode <= 49: print("Feature not available")Argument errors
Section titled “Argument errors”Arguments are parsed before the command runs. When one can't be parsed, the
CLI prints Failed to parse "<input>" for <argument>: <reason> and exits with
252, whatever the reason. This covers:
- unknown flags and missing required arguments
- invalid flag values, such as
--period bogusor--limit abc - invalid
<org>/<project>targets, such assentry trace list @latest
Run the command with --help to see the arguments it accepts.
- Exit codes below 128 are safe from collision with Unix signal exits (128+N).
sentry local runexits with your app's own exit code. If a signal kills the app, it exits 128+N, like a shell: 130 for SIGINT, 143 for SIGTERM. When you stop it with Ctrl-C or SIGTERM, it prints no error.- The
sentry apicommand renders API error responses to stdout and exits with code 60 (Output Error), not 30 (API Error). This matches thegh apiconvention — the error response body is useful output. Parse the HTTP status from--verboseoutput or the JSON error body if you need to distinguish API error categories. - Stricli (the CLI framework) uses negative exit codes (-5 to -1) for framework-level errors like unknown commands (251) or invalid arguments (252). These appear as 251–255 in unsigned form.