Business colleagues discussing paperwork around an office table
Illustrative stock photograph. Pexels. Not a product screenshot or evidence of a test.

SharePoint Approval ETag Mismatch: Check Whether the Reviewed Document Changed

An ETag identifies a particular state of a SharePoint document. If a content-approval flow fails after someone edits the file, do not simply replace its ETag with the latest value and approve blindly. First establish whether the approver reviewed the version now being approved.

Use an isolated test library and harmless documents for diagnosis. This article addresses SharePoint content approval through Power Automate, not every approval request shown in Teams or email. A human response and the library's content-approval state are related only when the workflow connects them correctly.

Trace the reviewed version

Record when metadata was obtained, when the approval request was created and when the document changed. Compare the file identifier and library as well as the displayed filename. A similarly named document is not interchangeable with the one attached to the approval decision.

Microsoft's content approval guidance explains obtaining an ETag from Get file metadata and using it with Set content approval status. It identifies the ETag as the specific version-related identifier needed in this document workflow.

Inspect changes during the waiting period

An approval can remain pending while authors continue editing. That creates a business question before it creates a technical retry question: does the response apply to the earlier material or the revised document? Preserve that distinction in the flow's state record.

Check your own flow updates

Metadata updates made by another branch of the flow can also matter. Review every action between the metadata read and the status update. Do not assume only a person opening Word can change the relevant item state.

Compare the inputs to the failing action

Inspect the exact site, library, item ID and ETag supplied to the action in the sanitized run history. The SharePoint connector reference describes metadata retrieval and content-approval actions. Use the relevant operation's fields, rather than substituting a path or filename where an item identifier belongs.

Keep concurrency evidence

If two runs act on the same document, record their timing and business state. A retry without coordination may compete with another approval or update. Stop duplicate processing in the test environment before deciding whether a stale value is the whole explanation.

FindingBusiness decision needed
File changed after review requestDoes it require a fresh review?
Flow updated properties while waitingDid that alter the state being approved?
Wrong item identifierCorrect the target before any approval retry
Two runs modify the same itemDefine ownership and concurrency handling
Office workers and equipment illustrating a digital document workflow
Illustrative stock photograph of workplace activity, not a product screenshot or a test result. Photo: Pexels.

Define an explicit stale-review branch

A robust workflow should detect that the material changed and route it according to policy. Options can include stopping for an owner review or starting a new approval cycle. Which is appropriate depends on the business process; the API cannot determine whether an edit was substantively important.

Refreshing metadata is not fresh consent

Reading the latest ETag may be technically necessary for a later operation, but it does not create a new human decision. Only use a current state after confirming that the workflow's approval policy permits the intended transition.

Keep the failure observable

Record that the update did not complete and notify the responsible owner through the approved route. Do not mark the process successful merely because the approver clicked Approve. The final library state must be checked separately.

Test edits at deliberate points

Create a sample request, edit its harmless document while the test approval waits and inspect the outcome. Repeat with no intervening edit. Confirm the changed-document case follows the defined exception path and the unchanged case reaches the intended content-approval state.

Our SharePoint approval workflow guide explains the distinction between review requests and library content approval. Use that model when documenting where the version check belongs.

Include a rejected-review case in the test as well. It must not reach the approved state after an exception handler or retry, even if the technical status update later becomes available.

Document revisions matter both during approval and during transfer. Review the related version-handling guide on SharePoint Copy To vs Move To: Version History.

Keep only a compact record of item identity, reviewed state, response and final transition. Avoid copying private document content into logs. The useful result is an approval process that can explain which material was reviewed and refuses to silently apply an old decision to an unreviewed revision.