caea47ec-7bdc-413c-ab9c-b58d9c814a83
# general-english
l
caea47ec-7bdc-413c-ab9c-b58d9c814a83
s
@Louis I just looked into the logs couldn't get useful information, can you share the complete curl request?
l
Copy code
{
  "name": "v33",
  "provider": "trieve",
  "searchPlan": {
    "scoreThreshold": 0.2,
    "searchType": "semantic"
  },
  "createPlan": {
    "type": "create",
    "chunkPlans": [
      {
        "fileIds": [
          "fe1fa798-482b-48ac-a710-454a828e1ef7"
        ],
        "websites": [],
        "targetSplitsPerChunk": 50,
        "rebalanceChunks": true
      }
    ]
  }
}
s
@Louis The payload is valid, can you share the complete request in DM.
We've noticed that when using our API key for creating a knowledge base, the request sometimes fails with a 403 error. The problem seems to be related to how our system syncs with Trieve, causing issues when the same key is used repeatedly. temporary solution: For now, please use your own Trieve dataset for the knowledge base. This workaround avoids the syncing issue and should let the KB process go through without errors.
s
I'm having the same issue, and just entered my Trieve API key, still having dramas
s
For now, please use your own Trieve dataset for the knowledge base. This workaround avoids the syncing issue and should let the KB process go through without errors.
@SteveCachia sorry for the typo mistakes in the above message.
s
The problem is my app, create KB on the fly, based on the user, so I need to change my entire code workflow for this to happen. How long do you think you are away from a fix?
s
@SteveCachia I will let you know, by checking with the team.
s
thank you