Assistant not accessing Knowledge Base
# support
d
v
message has been deleted
@Daniel F. It sounds like you've taken the right steps to configure your knowledge base with Trieve and associate it with your assistant. However, if the assistant is still unable to access the knowledge base information, there might be a few things to check: 1. **Knowledge Base Configuration**: Ensure that the knowledge base is properly configured with the correct
fileIds
that contain the information you want the assistant to access. 2. **Association with Assistant**: Double-check that the Knowledge Base ID is correctly associated with your assistant and that there are no typos or errors in the ID. 3. **Permissions and Access**: Verify that the assistant has the necessary permissions to access the knowledge base and that there are no restrictions preventing it from retrieving the information. 4. **API Calls**: Make sure that the API calls to the knowledge base are correctly formatted and include all required parameters. 5. **Synchronization**: After associating the knowledge base with your assistant, it may take a short period for the changes to propagate and for the assistant to synchronize with the new settings. If you've checked all these points and the issue persists, please provide me with more details about the configuration you've set up, such as the
provider
,
topK
,
fileIds
, and
maxTokens
you've used for your knowledge base. This will help me assist you further. If you're unsure about any of these details, please ask support for more info on this.
You can continue this conversation by mentioning me in the message.
d
FileIds is correct in the kowledgebase and Knowledgebase Id is correctly added to assistant model. TopK is not set for Trieve knowledge base maxToken in 300
s
Copy code
🟔 18:55:25:324 Error searching Trieve: {
  "message": {
    "message": "Request failed with status code 401",
    "data": {"message": "Unauthorized"}
  },
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 401\n
@Daniel F. You are using an incorrect KEY. Please verify your trieve Key once again.