[getConversationTags] Error getting conversation tags Error=2, Details='Response status code does not indicate success: BadRequest (400) #7328
-
What happened?I have the application deployed on Azure, using Azure Cosmos DB for Mongo as the database backend. Application seems to work fine, but I cannot create any bookmark and observe some errors in the backend: error message is:
Version Information0.7.8 Steps to Reproduce
What browsers are you seeing the problem on?No response Relevant log outputN/A ScreenshotsNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Azure CosmosDB is not officially supported, as we do not test or maintain for this integration. However, that being said, users report almost no issues when using vCore vs RU-based CosmosDB: https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/choose-model |
Beta Was this translation helpful? Give feedback.
-
@danny-avila @kbeaugrand I have seen this issue as well on my RU-based CosmosDB. It seems indexes are not added correctly at first startup. After restarting the api container about 3-4 times, the problem seems to be solved for me. |
Beta Was this translation helpful? Give feedback.
-
@danny-avila @kbeaugrand the problem here is that RU-based CosmosDB encounters rate-limiting while initializing the database and indexes, resulting in errors. |
Beta Was this translation helpful? Give feedback.
Azure CosmosDB is not officially supported, as we do not test or maintain for this integration.
However, that being said, users report almost no issues when using vCore vs RU-based CosmosDB:
https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/choose-model