Nested conditions fail with code "Badrequest"

[Hvantiel]

I currently have a flow with advanced conditions i would like to rebuild using nested conditions.

The flow:

When an existing item is modified

Condition : "Item1" contains "None"

- If Yes : Condition : "item2" is greater than

• if yes : create item in CRM
• If no : Send email

- If No : Send email

It already fails at the first condition with the following error:

The execution of template action 'Send_an_email' is skipped: dependant action 'Name' completed with status 'Failed' and code 'BadRequest'.

Flow guid:44771cfa-368d-4937-809e-5c2b1b69e7a1

Even a simple condition like @contains(triggerBody()['item'], 'None') fails.

 

[v-yamao-msft]

Hi Hvantiel,

Please provide some information about:
1.Did you configure your conditions in advanced mode?
2.After you received the “Bad Request” error message, did you try again with this flow? When you tried again with this flow, did it work well?
3.Did you try these actions in simple flows? Did these actions work in simple flows?

Best regards,
Mabel Mao

[Hvantiel]

Hi Mabel,

1. I tried a new workflow + condition using the GUI and the first time it runs, the second time it mails with the badrequest error.

 The advanced mode always seems to fail, even when copy pasting an existing advanced condition in a new flow.

2. The flow fails every time, even after en update.

3. I created a simple flow only with an e-mail action. Results are the same except for the first condition. This seems to work ok, but the second condition fails with error bad request. Weird thing is, i use the exact same condition in bot workflows ( added as advanced ) 1 fails, 1 runs.

Guid : 42f94738-850b-45c1-a032-ca4f5fab3576

Condition 1: @contains(triggerBody()['Verkoopkans'], 'Geen' ( made with existing advanced condition )

Condition 2 @contains(item()?['RFC_x0020_status']?['Value'], 'Nieuw') ( made with GUI )

[v-yamao-msft]

Hi Hvantiel,

I found an idea about Nested conditions at Flow Ideas which was submitted in May. Nested conditions should be supported by flow now. Here is a link of this idea:
https://powerusers.microsoft.com/t5/Flow-Ideas/Nested-conditions/idc-p/4863#M159

Then I tried to create several similar flows with you(with nested conditions) and I configured the conditions in normal mode. When the flow ran, I got the “Action Dependency Failed” error message on the last condition for each flow.

For this issue, please send a feedback by using the smile icon in flow.

Best regards,
Mabel Mao

[Hvantiel]

Hi Mabel,

I also found that article, i already use multiple conditions in expressions but i want to be able to create them whithin normal mode.

I haven't tried reusing the same condition in the second step, will try that today.

I currently use the following ;

@and(contains(triggerBody()['Attribute1']['value'], 'value1'), contains(triggerBody()['Attribute2'], 'value2'))

But I can only use the same condition "Contains". If i add an "Equals" within this expression the expression will fail.

For example:

@and(contains(triggerBody()['Attribute1']['value'], 'value1'), contains(triggerBody()['Attribute2'], 'value2'), Equals(triggerbody()['attribute3'], 'value3'))

I'm assuming this is due to an error in the expression, maybe you can help with that so i can continue.

I will send the feedback.

Thanks.

Regards,

Harm-Jan.

[Hvantiel]

It seems that flows are failing after a rename. Could this be possible?

When creating a simple flow with 1 condition, it works.

After renaming the flow, the condition is not met anymore and fails with "condition not met".

The flow does not run anymore.

Still haven't been able to use multiple conditions, the first one works, the second always fails.

Any suggestions? Feedback is given.

[efialtes]

@Hvantiel

Maybe there is a bug that currently makes imppossible to execute Advanced Mode edited Conditions, as suggested in

https://powerusers.microsoft.com/t5/Flow-Forum/Flow-Conditions-Instantly-Fail-In-Advanced-Mode/m-p/5...

I tried to define one yesterday, and it failed to execute. However, on May-June 2016 timeframe, Advanced Mode Conditions worked fine