Flow not triggering based on conditions

(0) Share

Report

Posted on by MN003

441

Good Morning,

I have one flow that doesn't trigger unless I manually test it or make an update to the condition and save. The flow has been successful in both cases previously mentioned. The fields that I'm using are valid and make sense, yet the flow just won't trigger. Whenever the flow runs it always says no inputs for the condition. Here is a screenshot of the flows and the columns I'm using for my flows:

Flow 1:

Sample of Flow 1 after making no updates to the condition and only clicking save:

List:

I'm not sure what else to do or if this may be a resource issue. I would appreciate any thoughts or guidance. Thank you.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (2)

Sort by

Verified answer

eliotcole 4,390 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi, @MN003, why not try adding each of those conditions as separate Trigger Conditions?:

@equals(triggerOutputs()?['body/IsSubmitted'], false)

@equals(triggerOutputs()?['body/IsDraftToSubmit'], false)

@equals(triggerOutputs()?['body/IsPreviousDraft'], false)

The above are examples of what I think your Trigger Conditions might look like ... but from what I see above they should work.

Because a Trigger Condition will stop the actual flow from running if it isn't correct, it could also save you flow runs in the process. You just tap the three dot menu on the Trigger itself, tap settings, then you can set three separate trigger conditions. Each separate condition must be met for the trigger to fire.

I'm sure you are aware ... but remember that you're running an AND condition here, so each of them need to be true (false! 😅) for it to be true overall. 😉

Also, check what values are reported from those fields, whether they resolve as a true boolean, or 1, or '1', or 'YES'/'NO' ... IRRC: Newer lists work with true booleans, but some older ones do not.

(that could be a load of codswallop, though 😅)

So, just do a Get items on the list to check what values it's reporting for those fields.

Was this reply helpful? Yes No
MN003 441 on at

Like (0)

Report
Copy link

Link copied!
Hi @eliotcole,
Thank you for chiming in and the suggestions. I got the below when I ran the Get Items, it looks like the fields I'm checking for would all result to true for the condition to pass 😣. I also added the three conditions separately, these three seem to work separately but how should the trigger condition look like for a choice field?

"Title":"Friday Test 1","DueDate":"2022-07-15","PriorApproval":false,"ApprovedBy":[],"ApprovedBy@odata.type":"#Collection(Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser)","ApprovedBy#Claims":[],"ApprovedBy#Claims@odata.type":"#Collection(String)","IsSupervisor":false,"IsCancelled":false,"EmailSent":false,"IsSubmitted":false,"runtheflow":"yes","IsDrafted":{"@odata.type":"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference","Id":1,"Value":"No"},"IsDrafted#Id":1,"IsPreviousDraft":false,"IsDraftToSubmit":true,

Was this reply helpful? Yes No
Verified answer

MN003 441 on at

Like (1)

Report
Copy link

Link copied!

@eliotcole,
I put this as the sole trigger condition and my flow finally works and triggers 😊:
@equals(triggerOutputs()?['body/IsDrafted/Value'], 'No')

Was this reply helpful? Yes No
eliotcole 4,390 Moderator on at

Like (1)

Report
Copy link

Link copied!

I would hasten to believe that you're fully sorted here, if your previous design was to get this to run with the 3 previous conditions.

Keep testing, just to be sure, mate.

If you're good after a nice bit of testing, then this is great news! 🙂

You just need to get to grips with what results you want, then you can set the conditions accordingly. 👍

Was this reply helpful? Yes No