Why is my Agent not using its Knowledge collection?

What I am trying to do

I created a course Agent from a template and linked a Knowledge collection containing several lecture PDFs. I want the Agent to answer student questions using grounded material from these files and cite specific sources.

What happened

The Agent provides generic answers without referencing the lecture notes. Sometimes it states that it lacks relevant information. Other times it generates fluently written explanations using general knowledge, omitting citations entirely.

What I tried

  • Confirmed processing. Every uploaded PDF displays a completed processing status in the collection interface.
  • Started fresh. I opened a new Chat and asked the same question again.
  • Compared against a direct upload. I attached a single PDF to the Chat window to see whether the answer changed.
  • Rephrased the query to match specific headings in the source document.

Environment

Detail Value
Role Faculty member
Agent creation method Created from Course Design template
Configuration Knowledge collection linked, web search disabled
Workspace Teaching Workspace within a campus Organization

Short answer

This usually comes down to one of three things: a collection that is linked but not explicitly enabled on the Agent, document text that is formatted poorly for retrieval, or Agent instructions that still allow answers from general model knowledge.

Why this happens

Agents do not automatically query every file in an Organization, and retrieval-augmented generation only pulls the passages that look semantically close to the question. Both of those facts show up as the same symptom: a fluent answer with nothing from your files in it.

Common causes

  • The collection is linked but not enabled. A collection has to be linked, enabled, and saved on the specific target Agent.
  • Query wording differs from the document text. Retrieval matches on semantic similarity, so a question phrased far from the source passage may retrieve nothing useful.
  • Another answer path is open. Retrieval runs on a linked collection without any Safeguard, but web search, URL browsing, or instructions that permit general knowledge all give the model somewhere else to go first.
  • Document processing did not finish. Incomplete processing prevents passage indexing.

What to do

  1. Enable and save the collection. Open Agent settings, verify that the Knowledge collection toggle is active, and click Save.
  2. Check file status. On the collection details page, confirm all files show a ready status rather than processing or failed.
  3. Probe retrieval directly. Ask a specific question that can only be answered by a unique paragraph in your document.
  4. Name the topic in your prompt so the retrieval context has something concrete to match.
  5. Close the other answer paths. Disable web search and URL browsing while you test grounding.
  6. Add the Knowledge Base Constraint Safeguard if steps 1 through 5 leave the Agent still reaching past the collection. This is the case the Safeguard exists for, and it works as prompt-level guidance rather than hard technical enforcement.
  7. Review retrieval threshold settings if they are configurable, balancing precision against broader semantic coverage.
  8. Check a duplicated Agent’s links. If you copied an existing Agent, confirm the linked collections came across.

How to verify

  • Your probe question yields an answer matching exact details from the source document.
  • Citations appear in responses when citation settings are enabled.
  • Questions outside the scope of the collection are declined when Knowledge Base Constraint is active.
  • A new Chat session reproduces grounded answers consistently.

If it still does not work

Create a temporary collection holding a single short text snippet, which tests indexing independently of PDF formatting. Also confirm that your account has editor permissions for the Workspace, since read-only users cannot modify collection links.

If issues persist, reply with your template name, collection processing status, and web search setting. Describe the documents in general terms, keeping confidential text, student information, and credentials out of the thread.