Support
Service Error Codes
Reference dictionary for service-level errors, severity metrics, and direct resolution pathways.
Reference list · Finkkle documentation
Common System Errors
Use the index below to map error returns from HTTP API responses or backend process logs:
| Error Code | Severity | Meaning | Resolution Action |
|---|---|---|---|
ERR_DB_CONNECTION | High | Process cannot open SQLite search.db file or connect to Turso endpoints. | Verify database file presence, check file permissions, or test TURSO_DATABASE_URL connectivity. |
ERR_AUTH_FAILED | High | Supabase authentication failed or session bearer headers are missing. | Verify header structure, validate authorization tokens, and verify Supabase credentials. |
ERR_UPSTREAM_TIMEOUT | Medium | Groq LLM service, Wikipedia API, or translation service did not respond. | Check internet connection, verify active environment API keys, and evaluate Phase 5 circuit breaker configurations. |
ERR_CRAWLER_BLOCKED | Low | Target domain robots.txt block or crawler IP rate limiting. | Modify crawler user-agent naming, increase delay intervals, or inspect target robots.txt file. |
ERR_CACHE_FAIL | Low | Redis connection failure or memory cache limits reached. | Check Redis server status, verify REDIS_URL, and run cache cleanups using npm run clear-cache. |
ERR_MODERATION_BLOCKED | Medium | OwlGuard moderation flagged search terms or results as explicit. | Verify SafeSearch parameters, check moderation queues, or adjust keyword blocklists. |
Query Support & Contact
If you encounter error conditions not listed here, or need clarification regarding Finkkle service behaviors, contact support directly:
Need Assistance?
Reach out to the team at [email protected] for service issues, API key verification, or general queries.