What Counts
Searches from your apps count only when a Workflow or Chatflow app’s Knowledge Retrieval node searches a classic knowledge base.Agent Knowledge Bases
These count:- Creating or deleting a knowledge base, changing its settings, managing its documents, sources, and metadata fields, and downloading documents.
- Each uploaded file, twice: once when you add it, and once when processing starts.
- Each sync you start in Dify.
- Each retrieval test, change to golden questions, and evaluation. Opening a golden question to edit it counts too, even without saving.
- Every Service API call, including reads. A streaming query counts once, when you start it.
- Searches from apps, through the Agent Knowledge Retrieval node or the new Agent.
- Scheduled syncs.
- Viewing a knowledge base and its documents.
- Reading a knowledge base through the Dify CLI.
Classic Knowledge Bases
These count:- Creating or deleting a knowledge base and changing its settings.
- Uploading, replacing, deleting, and downloading documents.
- Enabling, disabling, archiving, and restoring documents.
- Pausing, resuming, and retrying document processing.
- Adding, editing, enabling, disabling, and deleting chunks, including child chunks and bulk imports.
- Each retrieval test.
- Each run of a Knowledge Retrieval node, or each pass when the node sits inside an Iteration or Loop. A loop over many items can reach the limit on its own.
- Service API calls that change documents, chunks, or metadata, and each retrieval.
- Searches from Chatbot, Text Generator, and legacy Agent apps.
- Syncing Notion pages or websites, and adding documents by running a knowledge pipeline.
- Renaming a document, and managing metadata fields and values in Dify. Through the Service API, metadata changes count.
- Upgrading a classic knowledge base to an agent knowledge base.
- Retrieval tests on an external knowledge base.
- Changing document status in bulk or managing tags through the Service API.
- Viewing a knowledge base and its documents.
When You Reach the Limit
Once a workspace has used its limit within any 60 seconds, its next knowledge base request is refused. What you see depends on where the request came from:- In Dify, the action fails with an error message.
- Over the Service API, a knowledge base call answers 403 with the code
forbidden. - In a workflow run through the API, the failed Knowledge Retrieval node shows up in the run’s result or event stream, not as an HTTP error.