Inconsistencies in File Upload -> Queued/Processing

[microsoft]

Inconsistencies in File Upload -> Queued/Processing

[dayland]

@stu-ball , the UX upload feature uses the BlobServiceClient() to directly upload the files to Azure Blob Storage using a blob URI with SAS token.

The code in app/frontend/src/components/filepicker/file-picker.tsx calls a method in the backend App Service that generates a URI with SAS token using Azure Storage Account key credentials in app/backend/app.py.

You may need to think of an alternate pattern if you have CDN, APIM, or other proxy pattern in place.

[dayland]

@gitBenJo , after the file is uploaded to the Blob Storage into the "upload" container. An Azure Function is triggered by the upload of the file. This occurs before the file will be indexed by the Azure Search Indexer.

A couple things to check:

1. That the Function App Host in your Resource Group has "Always On" set to true.
2. Check the error logs for the Azure Functions by going to the Function App Host --> Go to the function "FileUploadedFunc" and check the Monitor tab. Here you can see exceptions if they are occurring.

[gitBenJo]

Thanks @dayland

@stu-ball can you reflect your findings here ... if we tried above, or what you saw even prior to the Azure Function trigger pls?

[stu-ball]

Thanks @gitBenJo - in our case it looks like the files aren't making it as far as the "upload" container, so the Azure Function isn't being triggered.
We don't have a firewall in front of the web app. We do have a (classic) Microsoft CDN in front, however we are still experiencing this intermittent issue even if we bypass the CDN.

[dayland]

This ticket is marked for closure due to inactivity in 5 days.

[gitBenJo]

@stu-ball , the UX upload feature uses the BlobServiceClient() to directly upload the files to Azure Blob Storage using a blob URI with SAS token.

The code in app/frontend/src/components/filepicker/file-picker.tsx calls a method in the backend App Service that generates a URI with SAS token using Azure Storage Account key credentials in app/backend/app.py.

You may need to think of an alternate pattern if you have CDN, APIM, or other proxy pattern in place.

@dayland - I believe @stu-ball implemented an alternate re CDN & our uploads now work more consistently. Thank you !!

[georearl]

Thanks. Closing