Power Automate

Error in codition when other user run this flow

(0) Share

Report

Posted on by angeldiaz96

Hello all i hope all well,

please help me with this case

For some reason, I'm getting this behavior in the condition when the user executes the flow.

The trigger is currently manual.

When I activate it with my user, it works correctly.

Any ideas about this?

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (0)

Sort by

David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

I am sorry, but what exactly is the behavior you expect and what is it that is not working? Based on your screen shots, I don't see any problems. The value in the condition on left comes from the user profile action and the value on the right is hard coded. What is the configuration of the get user profile action?

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

Question is not clear, but it senses me about configuration of scope like below :

or it is permission issue like below :

Reference : https://learn.microsoft.com/en-us/power-automate/create-team-flows#share-a-cloud-flow-with-run-only-permissions

Was this reply helpful? Yes No
angeldiaz96 57 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm sorry if I wasn't clear with the question.
In this screenshot, you can see that if I use my email as part of the condition, it works correctly.
With a different user (email), it does not send the email, and I am unable to view the details (Disabled grey ).

I only use GET PROFILE to get email and use in condition

Was this reply helpful? Yes No
David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Sorry, but your new post is no clearer than the first. How you have the condition configured, it is working exactly as you have designed it. The screen shot you uploaded does not show anything disabled gray. Do you mean that when someone else runs the flow, the condition does not go down the yes side of the condition? And therefore, the Email action on the yes side does not run? That would be expected based on your condition.

Why do you have the condition checking if the current user equals your e-mail address? That is why it does not send the e-mail when someone else runs the flow. Maybe if you explain the purpose of the condition, that will help us figure out what you're asking.

Was this reply helpful? Yes No
angeldiaz96 57 on at

Like
a
(0)

Report
Copy link

Link copied!

I need to include more than one condition, but for the moment I am just testing with a single one. So the condition are:

if the mail (GET MY PROFILE) is equal to user1.email.com, send an email using Template #1 (body) If it is false, it does nothing.

if the mail (GET MY PROFILE) is equal to user2.email.com, send an email using Template #2 (body). If it is false, it does nothing.

and if the mail (GET MY PROFILE) is equal to user3.email.com, send an email using Template #3 (body). If it is false, it does nothing.

When I run the flow, it works. (GET PROFILE Obtain my email)
but when other user run the flow (GET PROFILE Obtain her email), dont show error but dont send email and i can't see details (grey)... (check image)

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

When you say this "but when other user run the flow (GET PROFILE Obtain her email), dont show error but dont send email and i can't see details"

Can you please check the user and his/her email permission in the flow?

Was this reply helpful? Yes No
David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Now that I understand what you are trying to do, there is a much easier solution. Do this:

Delete the condition.

Replace it with a switch. Set the switch to the e-mail address value you are currently using in the condition.

Then add a case for each e-mail address (you can have up to 30 cases).

Then put the template for each person within the case.

Use the default for everything else. If you goal is to do nothing, you would put no actions in the default.

Was this reply helpful? Yes No