When running my Flow, I am not able to see the status due to the switch that I have in place (I think). Any way to fix that? I have multiple approvers that all must hit approve for my Flow to be fully approved, so I need to know who hasn't approved or who rejected.
Or could it possibly be my placement of the error handling action?
Pictures attached are of the Flow running and then the actual Flow.
Solved! Go to Solution.
This happens to the actions when inside a loop / switch when the flow has not finished yet.
Flow will not let you see the details of the run for who has approved and who hasn't.
Please consider voting for this idea, or creating your own in the ideas section:
Thank you! I voted for the idea - it would be extremely helpful.
Any thoughts on a work around or a temporary solution? My Flow has been running since 7/21 and not sure where it is "stuck". Before I go live with the Flow, I would like to find some sort of solution so we don't run into this while live.
There Is no easy solution here.
If you’re able to use CDS, all approvals and statuses are saved there. Although this would be a decent amount of work to implement this.
Are the approvers static? Do they change? You could setup a send email action before the approval starts, and sent yourself an email with the approver, than send yourself another email once that approver has actioned.
I like the idea of setting up an email action after the approver has actioned. How would I set this up? I have an action to send myself an email when the new approval process has started routing for approvals.
Approvals don't usually change. The only reason they would change would be best someone left the company/moved positions, which doesn't happen very often with this group of approvers needed.
Sorry, you will not be able to do this method. Only can do this if the approval has one approver. And multiple branches for each approver.
I will try and find a good example on the CDS method, would this be something you would want to implement, do you have access to CDS?
Jcook, thank you for your help on this!
What about if I broke it up like the attached picture? (I only put the send email notification with outcome on one approval, for now) Do you think that my condition will work with all the outcomes together (I ran into this issue in the past and that is why I put all the approvers back together)?
I'm not sure what CDS is - sorry, I'm pretty new to Automate!
It should work yes.
What issue were you running into before?
Just a quick question. Is what you're doing a requirement (being able to see who has responded or not to the approval?)
Once all the approvers have responded you will be able to check inside the flow history for all the details you want.
Also the flow will only run for 29 days than time out - so the approval can only be active for 29 days
Here is the link to the original flow that I created and the issue that I was running into: https://powerusers.microsoft.com/t5/Building-Flows/Error-with-multiple-parallel-approver-flow-when-a...
I was having issues with my condition of the approval outcomes. I have tried setting my condition to be "Outcome" is equal to Approve" and ""Responses" is equal to Approve" and received the error message both times. There is a screenshot of the error, but it said "no dependent actions succeeded".
I'm going to put all this together and give it another shot!
To answer your question, it is not necessarily a requirement, but I must have all approvers approve for the item to be completely approved.
This approval flow is for promotions that we are running for our company. Before they can be launched into the market, we must have approvals by various business units and they all must approve. For my automatic approval flow, the marketing manager creates a new item (promotion) within a SharePoint list. After the marketing manager creates the new item, it will automatically start a parallel approval process, with the approvers being dependent on the business unit/department which is why I have the switch in place. If it is a "RBU" promotion, those set approvers must approve vs if it is a "CABU" promotion, it has a different set of approvers.
@Jcook , I received the same error on my condition that I previously received (before moving all approvers together).
Any thoughts on the solution?
Pictures of how my Flow is structured and then the error that I receive.
Okay, so looking at your picture. It looks like the condition was successful. It was the send email action that failed.
could you go back into that run, and expand the send email action (the one with the red x) this should give more information on the error
@Jcook - thank you for all your help!
I looked there and I just forgot a semicolon in between my email addresses. Super easy fix and now it is working correctly!!
Again, thank you for all your help today!
Three Super User rank tiers have been launched!
Features releasing from October 2020 through March 2021
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!