Update Item Action Failing: Status: 400, Message: Exception from HRESULT: 0x80131904

[Anonymous]

I have a Production Power Automate workflow that has been running successfully since August 2023.

There have been no recent changes to the flow or the associated SharePoint list.

Suddenly on the morning of Oct 18, 2023 (9:02 AM Arizona time) I begin seeing workflow runs Fail.

I investigate and find that they are all failing at the same SharePoint Update Item action.

This Update Item action has worked successfully since the workflow went live in August.

As a test, I remove the action and re-submit the item.

This time it fails at the next Update Item action it encounters.  An update action that has always worked previously.

All of the failed workflows have the same (or similar) error message at the point of failure.

    Exception from HRESULT: 0x80131904

       clientRequestId: d15a1951-4a50-46a9-8f20-ffdd914e8075

       serviceRequestId: d15a1951-4a50-46a9-8f20-ffdd914e8075

{

  "status": 400,

  "message": "Exception from HRESULT: 0x80131904\r\nclientRequestId: d15a1951-4a50-46a9-8f20-ffdd914e8075\r\nserviceRequestId: d15a1951-4a50-46a9-8f20-ffdd914e8075"

}

Note:  Only the clientRequestId and serviceRequestIds were different between the error messages

The SharePoint Online list only has 163 items in it.

There have been no changes to any of the columns in the list.

Fields that are updated are the InstanceURL,  Status, WFState, TriggerWF, and Workflow History, etc., which are Single Line text or Multi Line text fields.

The workflow has previously been able to update the SharePoint list.

There are about 150 workflows running at the present time against items in the SPO list.

Does anyone have any idea what might be causing this issue?

[David_MA]

This may or may not be related. In addition to Power Automate, we use Nintex Cloud workflows. I am currently experiencing issues with update item actions there and the workflows are failing. Nintex indicates that the cause is 'User access token redemption failed', which seems like could be a cause in Power Automate as well. You can read Nintex's comments on this at Nintex Services.

However, if that is not the cause, I have a workaround for this, although I don't remember the actual error message I was getting for this. It usually occurs when someone has the item you want to update open in edit mode, which then prevents the workflow from updating the item.

If you want to give this a try, I put the Update item action in a do until action. Before this action I create a Boolean named Updated with a default value of false. Below the Update action, you add a parallel branch to set the variable to true or false. Update one of the Set variable actions to only run if the Update item action fails. Then below it, add a delay so it doesn't try again immediately. I set the Delay to 10 minutes and that has been sufficient.

A picture may make more sense:

[Anonymous]

Thank you for your quick reply.  The fact that you had a similar issue with Nintex Workflow Cloud SharePoint Update Item actions is interesting.  I see that there is still an active issue reported by Nintex and that they think it is an MS issue.  I am continuing to investigate.  I have a copy of the flow in dev/test environment and will see if I have the same issue there.  I have also opened a support case with MS.  I will post resolution once I have one.

[JimMoncrieff]

We're also receiving this error starting this morning Oct 18, 2023 (PST). It's occurring with SharePoint list updates that are called by the flow. It's intermittent with some flows and hapening every time on a larger flow we use. We're preparing to submit to Microsoft Support and will circle back with what we learn. 

[eileenoh]

We also started having this error today - 10/18/2023 - on an Update Item action in our power automate

[Anonymous]

Update:  Still no reply from MS support.

Not sure if this issue is related to the above, but it seems likely.

I have another standalone workflow that updates SPO list items in the same list as above issue.

The workflow populates a Word template and then converts the Word doc to a PDF, which is then added to a list item using the Power Automate SharePoint 'Add Attachment' action.  The flow was also working until 10/18.

The Add Attachment action fails, but with a different error.  Status 502 Bad Gateway.

[digitaldanlim26]

We also started having this error this morning - 10/19/2023 - Update Item action Step

[hulbertbn]

No response yet? I've started getting this problem on a Power Automate flow today.

[Anonymous]

No reply from MS Support yet.

[jakew2]

I'm experiencing the same issue. Multiple working flows that since today, are failing on the Update Item action.

[jaina]

I've encountered the same issue since yesterday October 18, 2023. Anyone who already resolved this??? 

[Oracle1]

Hi Everyone, 

I also have the same issue, all of my flow in power automate has an error in "Update Item"

    
Exception from HRESULT: 0x80131904
clientRequestId: 9cbfd37f-18ab-4b18-8155-b0a4c15e1a00
serviceRequestId: 9cbfd37f-18ab-4b18-8155-b0a4c15e1a00

{

  "status": 400,

  "message": "Exception from HRESULT: 0x80131904\r\nclientRequestId: 9cbfd37f-18ab-4b18-8155-b0a4c15e1a00\r\nserviceRequestId: 9cbfd37f-18ab-4b18-8155-b0a4c15e1a00"

}

[yerrojuanil2021]

Team,

We are facing similar issues on "Update Item Action" as shown below.

Please provide the any resolution. 

Action 'Update_item_
Exception from HRESULT: 0x80131904
clientRequestId: 9e11476f-cd7e-4303-b497-e44a55bec99e
serviceRequestId: 9e11476f-cd7e-4303-b497-e44a55bec99e

[jaina]

Same issue here. Still waiting for Microsoft to resolve the issue

[jaina]

Hello got a respronse from @Srini84

https://powerusers.microsoft.com/t5/Using-Flows/Exception-from-HRESULT-0x80131904-clientRequestId-03...

[Anonymous]

It looks like Nintex Workflow Cloud users are experiencing a similar issue with their SharePoint Update Item action.  Nintex have raised a Sev A ticket with Microsoft as the issue is originating from within SharePoint. 

Per Nintex Services page, "Microsoft support have confirmed that the issue being seen in Nintex Workflow Cloud SharePoint Update Item actions is as a direct result of the Microsoft 365 Suite Degradation MO682290."

Updates on MO682290 can be found in your Microsoft Office 365 Service Health Portal admin.microsoft.com/Adminportal/Home#/servicehealth/:/alerts/MO682290

[lmahumot]

I'm encountering this error in the Update Item action of my flow since this morning. It had been functioning smoothly for months, and neither the flow nor the SharePoint list have been altered recently.

[jaina]

Alert from Microsoft:

October 19, 2023 at 8:20 AM GMT+8

Title: Users may see failures occurring for some workflows and lists in multiple services

User impact:

Users may see failures occurring for some workflows and lists in multiple services.

More info:

This issue impacts specific SharePoint Online 2013 workflows on specific lists, Microsoft Power Automate workflows utilizing SharePoint connectors, and SharePoint Online lists which cannot be updated after Power Automate flows are executed against them.

For impacted Power Automate flows, users receive an error message stating "The file [file] has been modified by [user] on [date]."

More info:

This issue impacts specific SharePoint Online 2013 workflows on specific lists, Microsoft Power Automate workflows utilizing SharePoint connectors, and SharePoint Online lists which cannot be updated after Power Automate flows are executed against them.

For impacted Power Automate flows, users receive an error message stating "The file [file] has been modified by [user] on [date]."

Current status:

Our investigation has determined that a code issue caused a disconnect between two tables within the database infrastructure leveraged by your organization and is resulting in users being unable to edit existing lists as expected. We've developed a fix to prevent this disconnect from occurring, and we're implementing this fix in the affected database to restore service and remediate impact.

Scope of impact:

This issue may affect any user utilizing Microsoft Power Automate workflows utilizing SharePoint Online connectors, SharePoint Online 2013 workflows or SharePoint Online lists incorporated into Power Automate workflows.

Root cause:

A code issue caused a disconnect between two tables within the database infrastructure leveraged by your organization and is resulting in users being unable to edit existing lists as expected.

Next update by: Friday, October 20, 2023 at 3:30 AM GMT+8

[Anonymous]

Thanks

[Anonymous]

I received the standard "Hello, I am the Support Ambassador who has taken ownership and will be assisting you on your ticket. Can you tell me about the issue please." email on 10/19/23 at 2:18 AM (Arizona time).

It appears that MS has resolved the issue.

As of 10/19/23 at 4:30 AM (Arizona time), I was able to successfully run the flow for a new item I created.
I still need to see if I can Resubmit the flows that failed earlier and see if they succeed but will do that during my normal business hours (8-5 MST).  I'll report back later.