In this Microsoft flow, we will discuss how to solve error: The ETag of this item does not match the one used for setting content approval status. The contents of the item may have changed before the action was completed.
Recently, I was working on Microsoft Flow. As per my requirement, When a new file/document will upload to SharePoint Online Document Library, then the file will go to approve from the approver. Once the document will get approve/reject from the approver, then the user will get an email notification that his/her document has been approved/rejected.
Check Out Microsoft Flow and PowerApps Training Course (Lifetime Access)
Since I am uploading the file to SharePoint Online Document Library, It is going for approval from the approver. Here in my case, Approval works if the file is not open by the approver before it is approved. Once the file is open by the approver, then the file is not going to approve from the approver.
Below is the error screenshot once file is open before it is approved.
“{“Etag”:”\”{0261844A-9530-4840-9A79-1AF2A7946910},6\””,”Message”:”The ETag of this item does not match the one used for setting content approval status. The contents of the item may have changed before the action was completed.”

The ETag of this item does not match the one used for setting content approval status – Microsoft Flow
To solve this Microsoft Flow error, You have to add a “Set content approval status” action before using “Condition” action. In this “Set content approval status” action, you need to set the field values as below:
- Site Address: Provide your Site Address URL.
- Library Name: Specify the name of your Document Library.
- Id: Enter the document Id (metadata ID) from the Dynamic content.
- Action: Select the action as “Submit” from the drop-down.
- Comments: Enter comments from the approval action using Dynamic content.
- ETag: Enter the ETag of the file/folder from the Get file metadata action.
You can follow the below screenshot.

While the condition is approved, Take another “Set content approval status” action. In this action, all field values are the same as like previous one content approval status.
Here you just need to select the “Approve” in the “Action” field and enter the “ETag” value from previous “Set content approval status” which action value is “Submit“.

You may like following Microsoft Flow tutorials:
- Microsoft Flow Example: Copy files from one SharePoint Online account or folder to another
- Microsoft Flow Example: When an item is created in SharePoint List, Send approval and create item
- Microsoft Flow Example: When a message is posted on a group, Create a SharePoint list item
- Microsoft Flow Example: Automatically create a profile for a new candidate
- Microsoft Flow Example: Copy new files from your PC to SharePoint Online Document Library
- Microsoft Flow Example: Copy Files from SharePoint to PC
- Microsoft Flow Example: Email notification after approval from a SharePoint list
- PowerApps upload file to SharePoint Online document library using Microsoft Flow
- Microsoft Flow Example: Send a customized email when a new SharePoint list item is added
In this Microsoft Flow tutorial, We discussed the solution of an error as: ” {“Etag”:”\”{0261844A-9530-4840-9A79-1AF2A7946910},6\””,”Message”:”The ETag of this item does not match the one used for setting content approval status. The contents of the item may have changed before the action was completed.”
By using this above solution, You can overcome this type of flow issue.
Hello Everyone!! I am Bhawana a SharePoint MVP and having about 10+ years of SharePoint experience as well as in .Net technologies. I have worked in all the versions of SharePoint from wss to Office 365. I have good exposure in Customization and Migration using Nintex, Metalogix tools. Now exploring more in SharePoint 2016 🙂 Hope here I can contribute and share my knowledge to the fullest. As I believe “There is no wealth like knowledge and no poverty like ignorance”
Thank you, Bhawana! I’ve been trying to resolve this for days and no other solutions helped.
dunno if “get file metadata” wasn’t available back then, but by using it you avoid generating extra overhead and get the current ETag
Perfect:)
it does not work for me, anyone say diffrrent bullshit and diffrent method