Limitations & troubleshooting
Things to check when the Query Agent isn't behaving as expected, plus the soft usage limits and typical execution timings to keep in mind.
Usage limits
Each Weaviate Cloud organization can make up to 1,000 Query Agent requests per month at no cost.
Requests are consumed based on query type:
Ask: 4 requests per querySearch: 1 request per querySuggest Queries: 1 request per query
This limit may change in the future. For questions about usage limits, contact product@weaviate.io.
Custom collection descriptions
The Query Agent makes use of each collection's description metadata as well as individual property descriptions in deciding what collection to query.
Both collection descriptions and property descriptions can be updated after the collection has been created. For detailed instructions on updating collection and property descriptions, see the update collection definition documentation.
We are investigating an ability to specify a custom collection description at runtime.
Execution times
The Query Agent performs multiple operations to translate a natural language query into Weaviate queries, and to process the response.
This typically requires multiple calls to generative models (e.g. LLMs) and multiple queries to Weaviate.
As a result, each Query Agent run may take some time to complete. Depending on the query complexity, it may not be uncommon to see execution times of ~10 seconds.
For long-running or complex queries, consider using streaming responses rather than non-streaming requests. Streaming provides progress updates and sends heartbeats to maintain the connection, preventing timeout issues that can occur with long-running non-streaming requests.
Questions and feedback
If you have any questions or feedback, let us know in the user forum.