Error seen when deploying Chat using your own data App on Azure

Question

I am trying to deploy an app on Azure following https://learn.microsoft.com/en-us/azure/developer/python/get-started-app-chat-template?toc=%2Fazure%2Fdeveloper%2Fai%2Ftoc.json&bc=%2Fazure%2Fdeveloper%2Fai%2Fbreadcrumb%2Ftoc.json&tabs=github-codespaces

When executing azd up, I am getting the following error:

[06:48:38] INFO     Computed embeddings in batch. Batch size: 16, Token count: 2677                                                                  embeddings.py:117           INFO     Computed embeddings in batch. Batch size: 16, Token count: 2568                                                                  embeddings.py:117           INFO     Computed embeddings in batch. Batch size: 1, Token count: 112                                                                    embeddings.py:117           INFO     Uploading batch 1 with 305 sections to search index 'gptkbindex'                                                              searchmanager.py:507Traceback (most recent call last):                                                                                                                                      File "/workspaces/chat_app_azure/./app/backend/prepdocs.py", line 600, in 

Answer 1

Hi Dharmakumar Arumugam,

Thank you for posting on Microsoft Learn Q&A.

The issue is happening when the script tries to upload your documents into the Azure Cognitive Search index called gptkbindex. This usually means the index doesn’t exist yet, what the script is trying to upload.

To fix this Please follow the below points:

Go to the Azure Portal → your Cognitive Search resource → Indexes and check if gptkbindex exists.

If it doesn’t exist, run azd down --purge and then azd up again so the deployment can recreate it properly.

If it does exist but is broken, delete the index from the portal and re-run azd up so it gets rebuilt with the right schema.

Also double-check your .env file to be sure AZURE_SEARCH_SERVICE, AZURE_SEARCH_INDEX, and AZURE_SEARCH_API_KEY are pointing to the correct values.

Kindly provide me full error message after line 600 in, so I can help for the exact cause.

Hope this helps. Do let me know if you have any further queries.

Thank you!