expired
Token, challenge, or enrollment link expired.
On this page
HTTP 401 / HTTP 410challengepartner-2faapitypescriptjava
Code: expired · Shape: partner
Meaning
Token, challenge, or enrollment link expired.
Likely causes
- User took longer than the challenge window (~2 minutes at creation)
- Enrollment abandoned past enrollment TTL
- Consume attempted after token expiry
How to diagnose
- Inspect challenge/enrollment status (expired terminal)
- Note: HTTP may be 401 (token) or 410 (hosted link/challenge) depending on surface
How to fix
- Start a new enrollment or challenge.
- Improve UX so users complete within the window.
Retry behavior
Safe to start a new flow. Do not reuse expired ids/tokens.
Related
API: GET /v1/auth/challenge/{challengeId}, POST /v1/auth/challenge/{challengeId}/consume, GET /v1/identities/enroll/{enrollmentId}/status
SDK: waitForChallengeApproval(), waitForEnrollment(), pollChallenge()
Troubleshooting: partner-2fa
Guides: Authentication, Enrollment
