troubleshoot

# Troubleshoot DashClaw Systematic diagnostics for common DashClaw errors, signal anomalies, and configuration issues. ## Error Code Diagnostics ### 401 Unauthorized **Symptom:** API calls return `401`. **Checklist:** 1. Verify `x-api-key` header is set (not `Authorization: Bearer`) 2. Check `DASHCLAW_API_KEY` environment variable is set 3. Confirm the key hasn't been rotated — API keys are shown once at creation 4. Test with curl: ```bash curl -H "x-api-key: $DASHCLAW_API_KEY" $DASHCLAW_BASE_URL/api/health ``` **Root cause:** DashClaw uses `x-api-key` header, not Bearer tokens. The middleware does timing-safe comparison first, then falls back to hash lookup. ### 403 Forbidden **Symptom:** API calls return `403`. **Checklist:** 1. **Demo mode?** Demo mode blocks all write operations. Check `DASHCLAW_MODE` env var. 2. **Readonly key?** Some keys are read-only. Check key permissions in dashboard. 3. **Guard blocking?** If calling `/api/guard` and getting 403, a policy is blocking the action — this is working as intended. 4. **org_default trap?** The `org_default` org blocks API access except onboarding routes. Create a real org first. ### 429 Rate Limited **Symptom:** API calls return `429 Too Many Requests`. **Defaults:** - Production: 100 requests/minute per IP - Development: 1000 requests/minute per IP **Fixes:** - Set `DASHCLAW_DISABLE_RATE_LIMIT=true` for local development - For production: use `UPSTASH_REDIS_REST_URL` for distributed rate limiting - ...