Get Manager Failed (too many times)

[deCastroTony]

Hello all,

Today I'm stuck with a flow who collect the UPN of manager's.

In fact the flow is working fine when users have a manager but fails (the status fail) when users don't have a manager.

As my flow end every time as failed, after many try the flow is automaticaly desactivated.

I tried to add a condition.

if "get manager's" upn is "null" then "stop" i don't know how to stop.

if "get manager's' upn is not null then update the Sharepoint list.(this part seems to work)

 

Any idea ?

Many Thanks.

[Pstork1]

The key is to add a parallel branch and set it to run after the Get Manager failed.  Just make sure you either bring both paths back together or add a Terminate action set to Succeeded in the branch that runs after the failure.  If you do bring the paths back together make sure that its run after settings are set for Succeeded and Skipped.

[deCastroTony]

Hello @Pstork1,

Thanks for your answer, il will try to reproduce your tips.

Many Thanks.

[deCastroTony]

Hi @Pstork1,

I'm confused i think i don't understand how you want me to do.

As my scenario is under a loop each users who have a manager are updated fine.

I can say that this scenario is working well for my need.

As you said i try to add a parallel branch but with no chance..

I'm doing something wrong but i don't know what.

As he found users without manager the status is still ended as failed.

Resource 'manager' does not exist or one of its queried reference-property objects are not present

 

[Pstork1 · Accepted solution]

A couple things you will need to do.

1) It doesn't look like you are setting the RunAfter Settings on the parallel branches.  If you look at my example one of the branches has a red dotted line to it.  That indicates that it is set to run if the get manager fails.  If that one runs you either don't include the manager in the SharePoint update or you use some kind of default.

2) if you do a run after fail parallel branch you need to have some common action that runs after the fail.  This can be something as simple as a compose.  It just needs to bring the branches back together.  it will be set to run on success, or skip.

[deCastroTony · Accepted solution]

@Pstork1 

I solved my problem with your help.

It was just a problem with the RunAfter Settings misplaced 😉

I configure it directly in the parts Update SharePoint List.

Working for me.

Many Thanks.