749 B
749 B
title, category, error_codes, severity, owner, last_updated, status
| title | category | error_codes | severity | owner | last_updated | status | |
|---|---|---|---|---|---|---|---|
| Runbook — AUTH_TOKEN_EXPIRED (토큰 만료) | AUTH |
|
P3 | oncall | 2026-06-15 | stub |
Runbook: AUTH_TOKEN_EXPIRED (runbook://auth/token-expired)
Symptoms
- HTTP 401 with
error.code=AUTH_TOKEN_EXPIRED - Spike may indicate clock skew or long-lived token usage
Diagnosis
- Check
expclaim vs server clock - Check NTP sync on token-issuing host
Action
- Client must refresh tokens before expiry
- Verify clock skew tolerance is configured (default 60s)
Escalation
- Escalate if spike is widespread or clock drift is confirmed
Stub: Phase D2 — author body after domain adoption. (feature-operational-runbook-contract D9)