The unique AAD object ids for the two or more matching records are returned in the error message so that users can investigate further with a user administrator in their tenant.
![docsflow price docsflow price](http://emsoftware.com/wp-content/uploads/2012/06/Wimsatt-Rewards-Postcard-600x327.png)
Rather than potentially assign the approval to the wrong user account, Flow will fail the run. GraphUserDetailByEmailMultipleFoundįound multiple matching users (', ') for error will occur if two users in Microsoft Graph were found for the same Assigned To input (email address or UPN). This value should be populated with the approval id from Create an Approval. The record identifier passed to "Wait for an approval" is null, empty, or not a guid (in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). The provided record id '.' is null or invalid It will also be returned if multiple value users were specified for the re questor field. This error occurs if the input value(s) to the Assigned To field of the approval action was either not a well-formatted email address, UPN, or AAD object id, or it was well formatted, but didn't match any users in Microsoft Graph. The approval requestor must be a single, valid user account within your organization The Flow designer prevents any Flows from being saved without any value for this field, so typically this can occur if the Assigned To field is populated from the output of some other step and for this Flow run, there was no value for the expression or output field. This error occurs if the Assigned To field of the approval action didn't contain any values. Required field 'assignedTo' is missing or empty. If multiple users were specified (semi-colon delimited), then this means that all entries couldn't be found in Graph. This error occurs if the input value(s) to the Assigned To field of the approval action was either not a well -formatted email address, UPN, or AAD object id, or it was well formatted, but didn't match any users in Microsoft Graph. Required field 'assignedTo' contained no valid users in the organization This article introduces the common Power Automate approval errors and potential resolutions.Īpplies to: Power Automate Original KB number: 4513675 Assigned To and Requestor InvalidApprovalCreateRequestAssignedToNoValidUsers