Troubleshoot answer quality
Sometimes a Glean answer looks wrong, misses a document you expected, or ignores something you said earlier. Try the following steps to work out what happened, fix what you can, and report answer quality so Glean can investigate.
The answer looks wrong
Start with the citations. Every claim that Glean can support points to a source you already have permission to open, so the citations show whether the problem is the answer or the underlying content. See citations.
Select the inline citation markers in the response to see which document Glean used. Hover over a marker to preview the source in a card, and select the card to open the full document.
Open the original document and check the claim. If the source is outdated or contradicts itself, the answer reflects your content rather than an error in Glean. If the sources are correct but the answer misreads them, downvote the response (select thumbs down at the bottom of the response) and describe the difference. The Glean quality team reviews answer quality votes.
The answer is missing a document
Glean only uses content that is both indexed and visible to you, so a missing document is usually a permissions or timing gap rather than a bad answer.
- Check your access. Glean mirrors the permissions in your connected apps. If you can't open the document in its original app, Glean can't use it for your answer.
- Check whether the app is connected. Your admin controls which apps Glean indexes. Open Settings to see the apps you can connect.
- Allow for indexing time. For most apps such as Jira, Confluence, and Slack, Glean indexes new content within 15 minutes. For apps like Zendesk and Salesforce, API restrictions mean changes appear within an hour. If delays are longer than that, contact your Glean admin.
- Point Glean at the source. Type
@and select the document or person you want Glean to use, then ask the question again.
The answer is too broad or off-topic
Name the document, team, or date range you care about, or @ mention the source. Narrower questions produce answers that are easier to verify.
The tool did not run
If Glean returns instructions instead of doing the action in a connected app, and no Connect prompt appears, you're probably in a reasoning mode that doesn't load connected-app tools.
Switch to Thinking mode from the chat input and ask again. See reasoning modes and troubleshooting tools authentication.
Glean mixed up an earlier message
Memory and personalization have documented limits. Duplicate entries can appear and Glean consolidates them over time, and Glean consolidates new context about once a day, so Glean may not yet reflect something you said recently. Review known limitations, then check and edit your saved memories in Settings → Personalization.
To keep a single conversation on track, restate the constraint in your next message instead of starting a new chat.
The response was slow
Response time varies with the question, the reasoning mode, and how much content Glean searches. Deeper modes such as Thinking and Deep research take longer than Fast by design. Glean doesn't publish a response time target, and no setting guarantees one.
If a simple question is consistently slow, downvote the response so the timing data reaches the quality team, and tell your Glean admin.
Nothing in this list applies
Send feedback on the specific response. Detail is what makes it useful.
Downvote the response
Select thumbs down at the bottom of the response. A feedback form opens.
Say what you expected
Include the answer you expected, the document or system that holds the correct information, and which part of the response was wrong. Select a structured reason when one fits.
Submit
Glean sends the rating, your comment, and the related chat context for review. See user feedback for who can see it.
Feedback goes to review and troubleshooting. It doesn't retrain Glean's responses automatically, so don't expect the same question to change right away.
Escalate to a support ticket when the problem blocks your work, affects your whole team, or repeats across many questions. Your Glean admin files tickets for your organization. See create a support ticket.
See also
- Best Practices — how to phrase questions for better answers
- Citations — how to verify the sources behind an answer
- How Glean accesses information — what Glean can search on your behalf
- User feedback — what happens after you upvote or downvote
- Quick start guide — habits that produce better answers