HELP - Attachments are not (always) saved to SharePoint List

[Anonymous]

One of the users of my app ran into a problem saving a .pdf file of 5.6 MB in size as attachment to a SharePoint list item. I was able to reproduce the issue, but it's inconsistent. It works sometimes, but most of the time the attachment is actually not there after saving the record, and there is no error.

I tried with other files, and was able to upload files of 3 - 5 MB in size, but when it is over 5 MB, it sometimes happens that the attachment is not saved to the item.

The attachment control in the app is set to max 15 attachments and max 10 MB size (which is the imposed limit anyway). Is there some time-out threshold that prevents larger files from being saved if the network is slow?

Please help, this is a true show stopper. Thank you!

Edit: After some more testing I strongly suspect some time-out. Using a better Network connection I can upload larger files. Although on one occasion, a 7.8 MB file timed out after 2 minutes. I switched back to the "poor" network connection and both, the 5.6 MB original file and the larger 7.8 MB file time out after 2 minutes. How can I catch this time-out or whatever error it is and convey to the user?

[v-xida-msft]

HI @Anonymous ,

Could you please share a bit more about your issue?

Do you mean that the Attachments control within your Edit form could not upload a PDF file whose file size is more than 5 MB?

I have made a test on my side, and don't have the issue that you mentioned. Currently, within PowerApps, the maximum allowed file size in MB of each new attachment is 10 MB. Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-attachments#limitations

When you upload large files within your Attachments control, please make sure that your Network is in a good condition. Otherwise, you may face Request Time Out issue within your app.

If you want to capture the Request Time Out error within your app, I think the Developer tools of your browser could achieve your needs (on my side, I use Chrome😞

In addition, I also think the Fiddler trace tool could capture the Request Time Out error within your app. Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/gateway-reference#fiddler-trace

Best regards,

[Anonymous]

Thanks, "When you upload large files within your Attachments control, please make sure that your Network is in a good condition. Otherwise, you may face Request Time Out issue within your app." answers my question, but browser developer tools or Fiddler are not a solution (they just confirm the poor network condition, and may indicate where the bottleneck is).

How can I catch this error and pop up a message like "Your attachment could not be saved due to network performance issues. Please try again or try to reduce the file size." ?
The problem is that the OnSuccess event of the form fires even if the attachment upload timed out. There is no indication that it has failed, the attachment is just not there after the Edit Form closes.

[v-xida-msft · Accepted solution]

Hi @Anonymous ,

Based on the needs that you mentioned (e.g. "pop up a message like "Your attachment could not be saved due to network performance issues. Please try again or try to reduce the file size."), I afraid that there is no way to achieve your needs in PowerApps currently.

Currently, there is no way to capture the Time-Out error within a PowerApps app.

If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Fourm:

https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

Best regards,

[Anonymous · Accepted solution]

Thanks, I've posted the idea here https://powerusers.microsoft.com/t5/PowerApps-Ideas/Enable-catching-network-timeout-errors-when-savi...

[RameshMukka]

@Anonymous

I have exactly same issue. Have you found any solution or work around for this?

[fisko]

You just need to add a feature to increase the timeout of write to sharepoint. 1 minute is insanely low and completely useful for developing anything for mobile, which in the modern world is not a "nice to have".

[dbotache91]

Try disabling all Power Automate Flow or SharePoint workflows 2013 before performing the patch.

The issue arises because the SharePoint list record is being occupied by a flow. Check if you have workflows, especially those triggered by 'when an item is modified.' If the flow is making adjustments to the record, attachments may not be fully saved in the record. It's best to configure the flows to run after the patch and not use the 'when an item is modified' trigger.