I have inherited someone's flow, and it is throwing some errors in one of its decision branches. The workflow is quite simple and has something to do with a submission which requires multiple approvals. One of the approvals is showing "ActionFailed. An action failed. No dependent actions succeeded." and it is taking the wrong update into a Sharepoint field.
Can someone assist as I couldn't really figure out what went wrong?
Solved! Go to Solution.
Wow that is the biggest set of parallel actions I've ever seen ...
Uhhh, yeah, I think it's the update happening in the circle on the left that's causing the action in the circle on the right to fail.
A delay - maybe, that would be a good stop-gap - but ultimately I'd recommend (and of course this would depend on the full outputs of your flow) - to change this into a bunch of switch states rather than parallel. I'm also curious on why there's a parallel update of the same SharePoint item - I think a lot could be trimmed down here (but I know you've inherited the flow, this isn't on you!)
R
I'm seeing a Bad Request on that SharePoint Update - can you show us the error on the Flow Overview page? It should show up on the right hand side, under Error Details.
So, it's telling us that something else is trying to update this same item at the same time.
From your initial screenshot, it looks like a loooot of parallel actions. Are any other actions trying to update or interact with this same item in any way?
Yes @Rhiassuring. There are 7 approval branches and 2 conditional branches. I think the other conditional branch is updating the same item. Do you think putting a delay on this conditional branch would help solve the issue?
Wow that is the biggest set of parallel actions I've ever seen ...
Uhhh, yeah, I think it's the update happening in the circle on the left that's causing the action in the circle on the right to fail.
A delay - maybe, that would be a good stop-gap - but ultimately I'd recommend (and of course this would depend on the full outputs of your flow) - to change this into a bunch of switch states rather than parallel. I'm also curious on why there's a parallel update of the same SharePoint item - I think a lot could be trimmed down here (but I know you've inherited the flow, this isn't on you!)
R
Thanks @Rhiassuring , the 7 parallel actions don't actually involve a Sharepoint update rather, they just trigger an email notification. The 2 conditional branches are the ones making updates to the Sharepoint list item. I'll try to add a delay in the second branch and see how it goes. Thanks so much for your input, really appreciate it.
I think that'll probably solve your problem for now 🙂
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
12 | |
11 | |
9 | |
9 | |
6 |
User | Count |
---|---|
26 | |
20 | |
12 | |
10 | |
7 |