Azure Function not running for uploaded files making them unavailable to chat with

[frostedflakess]

Describe the bug A clear and concise description of what the bug is. I am receiving an error message when asking my Accelerator questions. Pictures included for reference on this issue.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error Error message show in screenshots when asking a question as well as when chatting.

Expected behavior A clear and concise description of what you expected to happen. I expected to receive an answer to my question referencing the PDF documents I had uploaded to my accelerator, however each time I am met with an error message. Screenshots If applicable, add screenshots to help explain your problem. Included above. Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22] Windows 11 Enterprise, 22H2 Version, Microsoft Edge browser Alpha version details
• GitHub branch: [e.g. main]
• Latest commit: [obtained by running git log -n 1 <branchname>

Additional context Add any other context about the problem here.

[oliverlabs]

I am facing a similar issue, once I upload a document, a green tick shows next to it. However, if I switch to the Upload Status tab, the list is empty.

Interestingly, if I go to an Azure Storage Account itself, I can see all the files uploaded there. Is there a way to solve it?

UPD: I redeployed into a newly created AOAI instance (instead of a pre-existing one) and it seems to be working. There's a minor delay while the Azure Function processes the document, but it works. I also had to replace the outdated davinci deployment model with chat-gpt35-turbo.

[dayland]

We are working to improve the “file status” to be more clear as well as moving to newer models in the next release, 0.3-Gamma.

[dayland]

Also the “Ask a question “ page will be retired in 0.3-Gamma in favor of the “Chat” page which can work the same way.

[bprerad]

I had a same error. What happens is that the function(s) that should be triggered once the file is uploaded to the "upload" container do not start processing the document. What I do, after the deployment is to restart the functions app through the portal and they start working as expected

[dayland]

We are addressing the function issue in 0.3-Gamma release. The issue was that the function was not marked with "AlwaysOn = true" thus it not starting right away and requiring it to manually be triggered. i.e. restart the function app.

[dayland]

Resolved in 0.3 Gamma release. Please update to the Gamma release.