simple condition fails (sometimes) with "no inputs"

(0) Share

Report

Posted on by Pion_G

Hello,
I've a simple flow, triggered by "When a new email arrives (V3)" condition, in a specific folder.

2nd step is a condition , combination of:

"subject contains"
"subject does not contains"
"body doesn't not contains"

That flow used to run (several times per day) without any issue until few days ago.

Recently it just stopped triggering. I've solved it by performing an "edit"/"test"/"save" sequence.

Unfortunately, since then, from time to time (not often but already occurred several times) the flow fails (status: "cancelled") with that error:

I have absolutely no idea how to fix this

All responses (16)

Answers (0)

dorenit 11 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

I had the same problem with one of my flows, after changing the condition input to the right "input" it wored. Check the "input condition" and change it.
KarlinOz 89 on at

Like (0)

Report
Re: simple condition fails (sometimes) with "no inputs"

This is interesting because I have a flow that does return both
{ "expressionResult": true }
and
{ "expressionResult": false }
in one condition block, depending of course on the inputs. However, the next condition block returns
No inputs
even though I have confirmed data points on the inputs do contain values. Interesting though, that, like @Pion_G, my triggers are a series of Or statements.
AllisterW 18 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

Hi

What did you do here? I think I am having same issue where expecting False (to lead down No path) but giving No Inputs... Yes very misleading if this is the case.

How did you get a false if doesn't match?
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

After more testing, it seem that the "no inputs" show up is when the condition do not match.
When it matches, raw input is:
{
"expressionResult": true
}

logically, I thought that when it doesn't, it should have been
{
"expressionResult": false
}
but this it not the case apparently! Inputs are null!
Very misleading.
So, there may be changes in the subjects of the mails I'm filtering which could explain what I'l seeing
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

@v-jefferni wrote:
If the issue persist, please consider raise a ticket on the support page:
https://admin.powerplatform.microsoft.com/support?newTicket&product=Flow

I"m unable to locate any "open/create/submit ticket" button on that page
It just show a blank page with "Welcome to the Power Platform support portal" text inside.

the "feedback" button opens a customer feedback survey.
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

Since the issue is in the "condition" step, the problem is not related to the Outlook connector
I've even used intermediate variables to make the condition based only on those variables, not the email trigger dynamic data.
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

I've deleted the "condition" et rewritten from scratch
And I still get "No Inputs" error from the condition
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

And now the flow don't even trigger anymore!
😟
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

Ok I've managed to delete the existing connexion, edit the flow to set up a new one (same credentials )
Testing the flow with a previous run fails identically.
I'm going to wait a little bit for a "normal" trigger
Pion_G 62 on at

Like (0)

Report

Re: simple condition fails (sometimes) with "no inputs"

@v-jefferni wrote:
Hi @Pion_G .

Have your tried to delete and recreate the connection?
https://admin.powerplatform.microsoft.com/support?newTicket&product=Flow

.
I don't have "connections" items in the UI but "connectors":
and it's content is different (its not my used connections but availables connectors)