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

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

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 (malformed ID, bad flag 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
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
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
61	Wizard Error	Interactive setup wizard encountered an error
62	Wizard Deps	Wizard dependency installation failed
63	Wizard Codemod	Wizard codemod plan or apply failed
64	Wizard Verify	User stopped wizard after verification step

Scripting Examples

Bash

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" ;;
esac

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")

Notes

• Exit codes below 128 are safe from collision with Unix signal exits (128+N).
• The sentry api command renders API error responses to stdout and exits with code 60 (Output Error), not 30 (API Error). This matches the gh api convention — the error response body is useful output. Parse the HTTP status from --verbose output or the JSON error body if you need to distinguish API error categories.
• The sentry init wizard maps its internal workflow exit codes to CLI exit codes: platform not detected → 20 (Config), dependency install failed → 62 (Wizard Deps), codemod failed → 63 (Wizard Codemod), verification stopped → 64 (Wizard Verify), other → 61 (Wizard).
• Stricli (the CLI framework) uses negative exit codes (-5 to -1) for framework-level errors like unknown commands or invalid arguments. These appear as 251–255 in unsigned form.