auth_code_expired
auth_code_expired
Section titled “auth_code_expired”HTTP status: 410 Gone
How to fix
Section titled “How to fix”- Re-run
jc auth login. The CLI generates a fresh device code and re-opens the authorize page in your browser. - Complete the browser approval promptly. Device codes expire 10 minutes after issue per RFC 8628 §3.2.
- For headless / SSH environments, use
jc auth login --no-browserand complete the verification on a phone — the device code is the same shape. - For CI/CD, don't use the device flow at all. Generate a long-lived API key in Settings → API Keys and set
JUSTCRAWL_API_KEYin the runner environment.
What this means
Section titled “What this means”You started a CLI login flow but didn't approve it in the browser within the 10-minute window, and the CLI tried to poll an already-expired code. We return 410 Gone (not 401) because RFC 8628 §5.5 specifies that expired codes should be terminal — the CLI stops polling immediately rather than retrying.
Related errors
Section titled “Related errors”auth_code_consumed— code was approved + used, can't reuseauth_invalid— long-lived API key is wrong/revokedauth_missing— no credential sent at all
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm when the code was issued and when it expired.