{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.connector-appears-connected-but-blocks","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"fm.connector-appears-connected-but-blocks","title":"A connector reports as already connected and still refuses to work","symptom":"GitHub shows as connected via Cursor, yet the Grok Bot connector demands a separate personal access token before it will do anything.","cause":"Grok Bot's connector is distinct from the Cursor integration and does not inherit its authorisation.","detection":"The task simply does not proceed. Reported independently by two hands-on testers eleven days apart.","fix":"Complete each Grok Bot connector's own auth explicitly rather than assuming an existing Cursor connection carries over. Related setup trap: a Slack trigger receives nothing until the connected app has been invited into the target channel.","severity":"low","source_id":"src.tp.4geeks.setup","source_url":"https://4geeks.com/en/blog/ai-tools/how-to-set-up-grok-bot","confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}