Is Glean Down?

If Prismix shows Glean as "Operational" but you're having issues:

• Search returning stale results (connector sync delay up to 24 hours) — Glean's data connectors crawl and index your connected apps on a schedule, not in real time. Newly created documents, Slack messages, or updated tickets may not appear in search results for up to 24 hours after creation. Check the connector sync status in the Glean admin panel to see the last successful crawl timestamp for each data source.
• Slack connector not indexing new channels (permission scope missing) — when new Slack channels are created after initial Glean setup, they are not automatically included in indexing if the Glean Slack app lacks the channels:history permission for private channels or if the Glean bot has not been invited to the new channel. Re-invite the Glean bot to newly created channels or update the Slack app's OAuth scopes in the Glean admin panel.
• AI Chat assistant citing removed documents (cache not invalidated) — Glean's AI Chat can reference documents that have been deleted or moved in the source system but not yet removed from Glean's index. The index purge for deleted content happens on the next full crawl cycle. If a sensitive document has been removed and Glean still surfaces it, trigger a manual re-crawl for that connector from the Glean admin panel.
• SSO login loop (SAML assertion expired) — if users are redirected back to the identity provider repeatedly without completing sign-in, the SAML assertion lifetime configured in your IdP (Okta, Azure AD) may be shorter than Glean expects. Extend the SAML assertion validity to at least 5 minutes in your IdP configuration, and ensure clock synchronization between your IdP and Glean's servers.
• User provisioning SCIM sync failing (attribute mapping mismatch) — SCIM provisioning failures typically surface as users not being created in Glean after IdP assignment, or user attributes (display name, department) not updating. Verify that the SCIM attribute mappings in your IdP match Glean's expected attribute names exactly, and check the SCIM provisioning error logs in the Glean admin console for specific rejected payloads.
• API bearer token rejected despite being freshly generated — Glean API tokens are scoped to specific data sources and actions. A token generated for read-only search access will be rejected with a 403 on write endpoints. Additionally, tokens tied to a deprovisioned user account become invalid immediately. Verify token scope in the Glean developer console and ensure the token owner's account is active and has the required permissions.