Unanswered

Flow does not always recognize the condition?

(0) Share

Report

Posted on by KAlexander_Engr

Hi - I am very new to PA so please be patient with me as I try to figure this out.

I currently have a condition that when someone puts a folder into teams it emails a specific person - I do not want it to email me for everything inside the folder so I came up with this flow.

1. This seems to work until I found my next issue...every email being sent was from me and not the person who created the file.

I then changed a few settings in my "Send an Email" this apparently just went completely awry and broke everything.

2. Now when I try to test my flow it doesn't even get past the the first condition - I place a folder into the perspective Teams file and it treats it as a not-folder and completes the loop.

PS I added another condition because some folders have folders inside of them that are named the same thing so I wanted that kicked out as well - this also worked. I am not sure at what point my flow decided that it was too smart for me.

Thank you to anyone who responds, in advance.

Screenshot 2023-0...

All responses (4)

Answers (0)

KAlexander_Engr 10 on at

Like (0)

Report

Re: Flow does not always recognize the condition?

I deleted my flow and tried to do this from scratch and it worked. I'm not sure what happened.
However the issue I'm running into now is it is sending me an email for EVERY folder within that newly created folder. Is there anyway I can just be emailed for the top level folder?

Thank you again
KAlexander_Engr 10 on at

Like (0)

Report

Re: Flow does not always recognize the condition?

Ali, thank you for replying! I verified that when hovering over the "IsFolder" it is displaying that.
I also tried your solution of @equals(triggerOutputs()?['body/(IsFolder)'], true) and it still does not work for me. When I go to test it the flow is stuck in a continuous loop.
AliB365 91 on at

Like (1)

Report

Re: Flow does not always recognize the condition?

Hi @KAlexander_Engr

Please can you check that the expression for your first condition is triggerOutputs()?['body/{IsFolder}'] by hovering your mouse over the dynamic pill for isfolder.

However, if you want to remove the condition entirely, you might want to consider a trigger condition. This can be accessed from the ellipsis (...) of the trigger, select settings, scroll down to trigger conditions, click add and then paste the following (including the @):

@equals(triggerOutputs()?['body/{IsFolder}'], true)

You will no longer need a condition and the flow will only run if a new folder is created, keeping your flow history clean.

If you've got any more questions please let me know. I hope this helps.

Ali B
KAlexander_Engr 10 on at

Like (0)

Report

Re: Flow does not always recognize the condition?

FYI for anyone asking for more info. This is what I get whenever I place a folder into teams to test it. It doesn't even get past the first condition.