I will explain more about what I am doing later but the end problem is when an upload from the site is initiated, a row in the note table is created but the “documentbody” is never populated (even after hours/days), meaning I have no data about the Azure details of the upload. I am estimating that this is happening about 7% of the uploads. I have located a few of the ‘blank’ note documents where there is data in Azure, but mostly it looks like the data hasn’t hit azure.
The only way that I can replicate this error is by killing the browser session before the content has finished uploading so it could be that the few ‘errors’ I am seeing are my users killing there session / network errors etc.
The main question is, is there any tracing / logs that anyone is aware of that the Power Platform keeps? I would assume that there must be a thread that times out if the user kills the session, thus Power Platform will not have committed this to Azure. I can find little or no information on how this process works, and how it can be debugged.
Background
To that end, I have created a cloud flow that is triggered when a note is created. I copy the key details from the note into other tables, and once that is done, the note is deleted. This means that user can upload as much as they need, in batches of 15. Mostly this is working fine.
It’s the cloud flow that spots that the “documentbody” is empty. The file name, size and all associated data with the note are there, except the document body (the base64 JSON details that Azure Blob passes back) is missing / blank.
I have put in retries and delays into the flow to see if the note is created before the upload is finished, but the notes without “documentbody” remain in Dataverse for weeks after the upload and the “documentbody” is never populated.