@Max Lacy we are sorry to hear you're facing this issue. Based on what you shared it seems like this problem is more related to Azure AI Search service rate limits rather than Azure OpenAI's rate limits. When you integrate Azure AI Search with Azure OpenAI in the playground, each query to generate a response typically involves multiple searches against your Azure AI Search index to retrieve relevant context.
There are a few potential rate limits that could be causing this:
- Queries Per Second (QPS) limit: Azure AI Search has different QPS limits based on your service tier:
- Free tier: 3 QPS | Basic tier: 15 QPS | Standard S1 tier: 25 QPS
- Higher tiers have progressively higher limits
- Also, there might be a limit on how many documents can be extracted per query.
To troubleshoot you should:
- Check your Azure AI Search service tier. If you're on a lower tier, you might need to upgrade to a higher tier with better rate limits.
- Look at the Search service metrics in Azure Portal to see if you're hitting QPS limits.
- You could implement retry logic with exponential backoff in a production environment, though this isn't applicable in the playground.
- Consider adjusting the number of documents retrieved per search or the number of searches performed per query if possible.
- You might also want to check if there are other processes or users querying the same Search service
Hope that helps.
-Grace