Unanswered

Trigger Condition Fails Silently

(0) Share

Report

Posted on by JFZoidberg7975

I built a flow that emails posts in a specific Teams chat (not a channel). It works, but it's triggering on every chat conversation I'm in, filling the audit log with junk entries every time I get ANY chat message.

When I add the conversationID as a trigger condition the flow never runs. I don't believe the syntax for the conversationID is wrong. Here's the trigger (with a placeholder for the actual conversationID):

@equals(triggerOutputs()?['body/conversationID'], 'PLACEHOLDERcoversationID@thread.v2')

I've been using https://www.spguides.com/power-automate-trigger-conditions/ as a guide for writing this trigger and it doesn't seem I've done anything wrong. My only other other thought is that my organization might be inadvertently blocking the trigger condition with some security setting.

I tested other simpler triggers and they also fail.

Here's an example of a response. I made sure my trigger condition matches the conversationID from the desired chat as displayed in this response.

{
 "headers": {
 "Expect": "100-continue",
 "Host": "xxxx.xxxx.xxxx.azure.com",
 "X-Forwarded-For": "XX.XX.XX.XXX",
 "Content-Length": "1098",
 "Content-Type": "application/json"
 },
 "body": {
 "value": [
 {
 "subscriptionId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
 "changeType": "created",
 "clientState": "secretClientValue",
 "subscriptionExpirationDateTime": "2023-10-19T16:26:40.9326058+00:00",
 "resource": "chats('PLACEHOLDERconversationID@thread.v2')/messages('1697732435167')",
 "resourceData": {
 "id": "1697732435167",
 "@odata.type": "#Microsoft.Graph.chatMessage",
 "@odata.id": "chats('PLACEHOLDERconversationID@thread.v2')/messages('1697732435167')"
 },
 "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
 "conversationId": "PLACEHOLDERconversationID@thread.v2",
 "messageId": "1697732435167",
 "linkToMessage": "https://teams.microsoft.com/l/message/PLACEHOLDERconversationID@thread.v2/1697732435167?tenantId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&context=%7B%22contextType%22:%22chat%22%7D"
 }
 ]
 }
}

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

wskinnermctc 6,519 Moderator on at

Like (1)

Report

The body you provided shows "conversationId" but your trigger condition is using "conversationID"

Try it without the "D" capitalized and see if that helps.

"conversationId" - is not same as - "conversationID"

I don't know if that is the issue, but just something I can see from what you provided.

Was this reply helpful? Yes No
JFZoidberg7975 10 on at

Like (0)

Report

Thank you for spotting that typo, but it doesn't change the result.

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (1)

Report
One thing you could do is run a test flow and put a compose action. In the compose action write an expression to the same one you want to use as the trigger condition. The expression in the compose step should have the same results as if it was in a trigger condition.

So like add a compose, and then the expression for the compose put:

equals(triggerOutputs()?['body/conversationID'], 'PLACEHOLDERcoversationID@thread.v2')

Run the flow and see what that output looks like.

Also in this post about trigger condition made easy - it shows using

@equals(triggerBody()?['RunAutomation'],true)

so for you that would be

@equals(triggerBody()?['conversationID'], 'PLACEHOLDERcoversationID@thread.v2')

I don't know how much of a difference that makes

Was this reply helpful? Yes No
JFZoidberg7975 10 on at

Like (0)

Report

I switched the trigger to "triggerBody" to no avail. Also, when adding the "Compose" step, I get a "false" result.

I assume this means that Power Automate believes that statement to be false (even though it is in fact true).

Was this reply helpful? Yes No
JFZoidberg7975 10 on at

Like (0)

Report

I did notice that, in the trigger condition made easy post there was a step I was skipping;
I was not turning this option on. However, when I did, I got a different result than the one pictured here. I could only choose "@triggerBody()?['body/value']". After saving it and noticing the flow stops running, when I go back to edit the flow only then do I see the warning that the split is unsupported.
I am guessing that enabling the split is essential to filtering, but if my instance won't recognize my only split option, I'm essentially dead in the water.

Was this reply helpful? Yes No