glean-common-errors

# Glean Common Errors ## Overview Glean provides enterprise search across connected data sources with AI-powered results. API integrations involve two distinct token types (indexing vs. client) and a custom datasource model for pushing content. Common errors stem from token type mismatches, permission misconfiguration that silently hides documents from search results, and bulk indexing failures caused by duplicate upload IDs or oversized documents. Stale results are a frequent complaint -- Glean indexes asynchronously, so newly pushed documents may take 1-5 minutes to appear in search. This reference covers authentication, indexing pipeline, and search-time issues. ## Error Reference | Code | Message | Cause | Fix | |------|---------|-------|-----| | `401` | `Unauthorized` | Invalid or expired API token | Regenerate at Admin > Settings > API Tokens | | `403` | `Wrong token type` | Using indexing token for search API | Indexing API needs indexing token; Client API needs client token with `X-Glean-Auth-Type: BEARER` | | `400` | `uploadId already used` | Duplicate bulk upload identifier | Generate a unique UUID per upload run | | `400` | `document too large` | Document body exceeds 100KB limit | Truncate or split content before indexing | | `400` | `invalid datasource` | Datasource not registered | Create datasource first via `adddatasource` endpoint | | `400` | `missing required field` | Document lacks `id` or `title` | Ensure every document has both `id` and `title` fields...