RAG Forget Component
Use the RAG Forget component to permanently delete a specific piece of information from your agent's knowledge base. By providing a unique Source Identifier
, you can instruct the agent to remove outdated, incorrect, or irrelevant data.
Why this matters
What You’ll Configure
Step 1: Specify the Target Data
Tell the component exactly which piece of information to delete by specifying its Namespace
and unique Source Identifier
.
Setting | Required? | Description |
---|---|---|
Namespace | Yes | Select the knowledge base (namespace) from which the data source will be deleted. |
Source Identifier | Yes | The unique ID of the data source you want to delete. This must exactly match the identifier used when the data was stored, typically with the RAG Remember component. |
Dynamic Deletion
Step 2: Handle the Output
The component provides a simple success or failure indicator for the deletion operation.
Output | Description |
---|---|
Success | Returns true if the data source was successfully deleted. Returns an empty value if the deletion fails (e.g., the identifier was not found). |
Best Practices
- Verify Before Deleting: This action is permanent and cannot be undone. It is a good practice to use the RAG Search Component first to confirm you have the correct
Source Identifier
before deleting. - Implement Data Retention Policies: You can create time-based workflows that automatically delete data after a certain period. Use a database to store identifiers and their creation timestamps, and have a scheduled agent run daily to forget expired entries.
- Build User-Facing Deletion Flows: Allow your users to manage their own data by creating an Agent Skill where a user can provide an ID, and your workflow uses
RAG Forget
to process the deletion request.
Troubleshooting Tips
If data is not being forgotten...
What to Try Next
- Create a complete data management workflow by combining RAG Remember, RAG Search, and
RAG Forget
. - Build an agent skill that allows an administrator to provide a
Source Identifier
and have the agent confirm the deletion. - Use this component as part of a GDPR or CCPA compliance workflow to handle user data deletion requests.