Answered

Save Conflict on Email Attachments to SharePoint library

(0) Share

Report

Posted on by Tcamozzi

Hourly an email with 3 attachments is sent and by rule sorted into a specific inbox folder. The flow will copy the attachments to a SharePoint library, overwriting the existing file so that only the most recent version of the data is available. The flow is succeeding and failing. Rerunning failed flows instances = success. Failed runs show a Save Conflict error. Reviewing the version history of the document I expect to see one new version every hour on the hour (or close enough.) Instead I see gaps where there is no version (probably when the flow failed) and 2-3 versions created in the same minute.

Thanks for the assistance.

Run historyerror message on failed runversion history of doc shows sporadic flow activity

Categories:

Using flows

I have the same question (0)

All responses (5)

Answers (1)

v-yamao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Tcamozzi,

Staring the flow from the “Save my email attachments to a SharePoint document library” to test this issue, I am not able to reproduce it on my side.

I send an email with the same attachments for several times, every time the flow runs succeed and all the attachments can be saved to the library successfully.

When checking the Version history of the files, the old version has been replaced by the latest version.

Please try to resubmit the run on your side. More details about resubmitting a flow, please check it at here:
https://flow.microsoft.com/en-us/blog/managing-runs/

Best regards,
Mabel Mao

Was this reply helpful? Yes No
Tcamozzi 13 on at

Like (0)

Report
Copy link

Link copied!

My test also ran fine for a bit. Then failed runs started. I can resubmit the failed run and the flow is successful.

Since these documents are updated hourly 24/7, a manual fix isn't sufficient. The work group that references these documents is also staffed 24/7. I then was wondering if someone is in the document when it is being refreshed by the flow. However in my test copy of the flow pointing to a test library that most likely no one knows about, I still get failures.

Was this reply helpful? Yes No
v-yamao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Tcamozzi,

Please provide your Flow Id, I will help confirm it on my side.

To get your Flow Id, in Edit mode, copy and paste the URL at here.

Best regards,
Mabel Mao

Was this reply helpful? Yes No
Tcamozzi 13 on at

Like (0)

Report
Copy link

Link copied!

My copy of the flow that ran without fail for most of the weekend: https://us.flow.microsoft.com/manage/environments/Default-0f44c5d4-42b0-45c2-bf55-d0fea8430d33/flows/5b7f61e5-58a6-46b2-9bce-0cf63f2708d4?backUrl=%2Fflows%2F5b7f61e5-58a6-46b2-9bce-0cf63f2708d4%2Fdetails

The flow in production that had a number of fails over the weekend: https://us.flow.microsoft.com/manage/environments/Default-0f44c5d4-42b0-45c2-bf55-d0fea8430d33/flows/shared/c27e69d2-5a42-4eb8-a3f2-0166b1e58081?backUrl=%2Fflows%2Fshared%2Fc27e69d2-5a42-4eb8-a3f2-0166b1e58081%2Fdetails

Thank you very much for the assistance on this!

Was this reply helpful? Yes No
Verified answer

Tcamozzi 13 on at

Like (0)

Report
Copy link

Link copied!

We figured out that the end user was forwarding (not moving) the email from his inbox into a folder. Consquently the flow was running on each instance of the email (so twice) and causing file writing conflicts in the library. We updated the flow to look for and ignore any emails with FW: in the subject line. Now it is running consistently without save conflicts.

Was this reply helpful? Yes No