We have set up a very simple work flow to get mail-attachments from a shared mailbox and save them into a specific SharePoint folder. There is nothing special configured, just the normal use case.
When processing attachments (PDF files) with sizes smaller than 5MB, the attachment file appears in the SharePoint folder within 1-2 minutes after e-mail fetch is triggered.
When processing attachments (PDF files) with sizes larger than 10MB (we have some attachments with sizes up to 25MB), it lasts up to more than 1 hour, until the file appears after e-mail fetch is triggered.
The Screenshots show the workflow parts and the execution times (successful) for attachment sizes with max. 20MB - there was one mail attachment processed with each trigger. if a process takes a long time (e.g. 2h), all subsequent processes are delayed by this time.
What causes this long processing time, is there a way to solve this or is this a fundamental problem with handling "large" mail attachments (> 10 MB)?
@annajhaveri the subsequent steps in flow do not depend on saved attachments in SharePoint: We use this process to deliver scanned documents one-by-one from the scanner to SharePoint via mail, as direct scan to SharePoint is not yet supported. Documents will be removed manually by users (or housekeeping) afterwards. Even if documents are processed parallel, the delivery of one document may take more than 1h (obviously depending on its size).
@Thomas_Meier are the subsequent steps in flow depending on those attachments saved in SharePoint? If not you can keep those as last step or add parallel step in flow to do add actions in flow
WarrenBelz
146,645
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,997
Most Valuable Professional