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.