Before you begin
You need access to the document’s workspace and permission to manage knowledge. Keep the document ID and the original source. For initial creation, follow Knowledge base.1
Inspect the document
Read document metadata and stored content. Check the type, intended source, and whether the stored representation includes the facts the agent needs.A folder organizes documents; it does not have document content of its own.
2
Review dependencies
Use List agents using a document. Follow
next_cursor while has_more is true. Keep the same filters when requesting another page.The list covers active agent references and related nonarchived branches. It is not a complete historical-version inventory. Review relevant saved versions separately before a destructive change.3
Choose the matching change
Use the operation below for the source type. Review the proposed replacement before sending it; editing a shared document is different from changing an agent’s attachment list.
4
Read the result back
Check the returned status, metadata, and stored content. Review indexes and any affected agent references separately. A successful update does not prove that a live conversation is using the new information.
Choose an operation
Do not use a force-delete option merely to dismiss a dependency conflict. Decide how the referencing agents should change first. Bulk operations can report a different result for each item; inspect every result before treating the batch as complete.
Frequently asked questions
Does replacing a file prove retrieval is ready?
Does replacing a file prove retrieval is ready?
No. Inspect stored content and the relevant index state, then review RAG. Source storage and live retrieval are separate checks.
Does a URL document stay synchronized automatically?
Does a URL document stay synchronized automatically?
Do not assume that it does. Use the explicit refresh operation where supported and read back the content you intend to use.
Why is the dependency list empty for an old version?
Why is the dependency list empty for an old version?
The dependency list is not a complete historical inventory. Inspect the version’s saved knowledge locators directly before deleting a source it references.