Requestor field for Approval will not set

[Perceptus]

I am using a start and wait for Approval object in my flows.  After the first set of approvals goes, it triggers an HTTP Post request to fire off the next approval flow.  On the next approval flow I cannot set the requestor field, I have even tried setting it to the static value of my email address instead of dynamic content relayed between flows.  It does not work.  I get 

User lookup request to Graph failed lookup for user identifier: ''. 

The forums say it needs to be filled in, but it is already?

[SudeepGhatakNZ]

Looks like the user information is not getting sent via the HTTP action.

Have you checked the inputs of your HTTP trigger?

[grantjenkins]

Are you able to send through a screenshot of your flow to see exactly where it's failing and a copy of the error, etc.

Given that you said it even fails when you hard code your email directly into the flow itself indicates it's not the HTTP trigger that has the issue, but something in that flow.

[Perceptus]

Gladly, its odd where it has problems.  The 1st flow uses all the same logic, infact this flow is a copy of the 1st flow, with just some changed approval users and it triggers on http request.

[SudeepGhatakNZ]

@Perceptus ,

I will be keen to look at the trigger inputs and outputs.

As you say the two flows have different triggers, so that is what you should investigate.

[Perceptus]

the trigger inputs are passed without a problem.  I send the HTTP request and have a schema for it based on the payload. it works without a problem.   the issue happens because the requestor field is saying its empty, even though I have it plugged with a static email address. 

[grantjenkins]

Is it possible to delete that particular action and add a new one? Sometimes they just get corrupt and recreating it can magically fix the issue - worth a shot if not a lot of work.

[Perceptus]

Unfortunate it did not work.

[grantjenkins]

Not sure if you've got this working yet. If not, can you confirm that it doesn't work even if you have the same approvers as the other flow (the original one that works)? Just trying to understand if it fails for all users you try (in both the Assigned to and Requestor fields).

If you've swapped out the entire Approval action, then still think it's something related to the users you're adding in. For the user(s) that are failing, are you able to add them to a Get user profile action to see if that also fails.

[Perceptus]

It is not working. I have set the Approval and Requestor fields static to myself and its still doing the same thing.  It fails regardless of the values I set the fields two, but only in the 2nd flow. 

I have a ticket open with MS Support and they are working with me on it.  Will post back when they figure it out.

[grantjenkins]

Hopefully they can get it sorted for you.

Have you tried saving a copy of the flow and seeing if the copy still has the same issue? Worth a shot.

[Perceptus]

Turns out, that in the condition there was a section that responds to the recipient that wasnt copying over from the previous flow. It has a field called Recipient, which was empty and giving the error that lead me here.