Unanswered

When keywords are mentioned - Failing

(1) Share

Report

Posted on by GregoryMelo

Hi, friends!

I have some flows that use the Teams trigger "When keywords are mentioned". They were running perfectly, but sudenly they are failing. Without any modification in Power Automate or Teams, they just stopped and show the message: There's a problem with the flow's trigger.

I read this document (There is a problem with the flow's trigger - Power Automate | Microsoft Learn), however, there is nothing to do to fix this problem.

Could someone from Microsoft help me?

Thanks!

Categories:

General topics

I have the same question (0)

All responses (8)

Answers (0)

Pstork1 68,697 Most Valuable Professional on at

Like (2)

Report

Check to make sure the flow hasn't been turned off, due to failures, or that the authentication is still valid on the Teams connector. Those are the two most typical issues. Could you post a screenshot of the Trigger?

Was this reply helpful? Yes No
GregoryMelo 12 on at

Like (0)

Report

Thanks for support, however, the flows were not turned off and the authentication was valid.

After I turned off them, I turned on and now the flow is running. I dont know if will be running for a long time, but they are working as expected. If they start to fail again, I will send a message here.

**

The code:
{
    "inputs": {
        "host": {
            "connectionName": "shared_teams",
            "operationId": "WebhookKeywordTrigger",
            "apiId": "/providers/Microsoft.PowerApps/apis/shared_teams"
        },
        "parameters": {
            "threadType": "channel",
            "$search": "avisarcanal",
            "requestBody/groupId": "178f1075-355f-4b74-aba8-d3abcf2c3c94",
            "requestBody/channels": [
                "19:88b6bcf0ce8a4ab1a960327645613b85@thread.tacv2",
                "19:97729d09da0e4814ac7b45f5bbe1380e@thread.tacv2",
                "19:f984111c0de74e91a810a463d419721c@thread.tacv2",
                "19:3ba47804b3d64d0d9b7a80d30050f3ed@thread.tacv2",
                "19:9b3435acbb17415ba86e931f51b39788@thread.tacv2",
                "19:eb0d0e91bf9a4550afe091aa6fccf495@thread.tacv2",
                "19:aab22fdf212c4f28850fc407e87ca241@thread.tacv2"
            ]
        },
        "authentication": "@parameters('$authentication')"
    },
    "metadata": {
        "operationMetadataId": "b2b9fb68-59cd-4939-a769-baf69d559d76"
    }
}

**
The print:

Was this reply helpful? Yes No
GregoryMelo 12 on at

Like (0)

Report

Hey, my friend!

The flow stopped again. It is important to say that I did not make any change in the Teams channels.

Error message:

{"responses":[{"id":"0","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:05","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"2","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:05","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"3","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:05","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"6","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:06","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"4","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:06","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"1","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:06","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}},{"id":"5","status":404,"headers":{"Cache-Control":"no-cache","Content-Type":"application/json"},"body":{"error":{"code":"ResourceNotFound","message":"The object was not found.","innerError":{"date":"2023-04-27T01:51:06","request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b","client-request-id":"6b27406b-9de0-4603-a6b6-f317eaf4d50b"}}}}]}

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

I think for this one you'll need to open a support ticket with MS. I don't see anything specifically wrong with the flow. Nor is there anything in the error message that suggests what the problem is.

Was this reply helpful? Yes No
tstad 2 on at

Like (0)

Report

I have the exact same issue. Periodically it fails and reports a problem with the trigger.

The output is 404, object not found. Did you get any answer from MS?

Was this reply helpful? Yes No
GregoryMelo 12 on at

Like (0)

Report

Hi,

I tried two times, but they do not what are causing this provisioning trouble. 😕

Was this reply helpful? Yes No
RickTurpin 2 on at

Like (0)

Report

HI I have the same problem and in my case it is relating to the subscription ID being used for the Trigger to monitor the teams channel. Periodically (2x this year so far) the flow will lose the token for the subscription and stop listening to the channel. The good news is the work around is fairly simple. The bad news is there is no warning when it is going to happen next. My flow was working last Friday and Not working Today (Monday). Something broke over the weekend. Here is how I fix the problem. Edit the failing flow, open the Trigger and modify the list of keywords (in my case I added an additional keyword "test") Save the flow. This will re-establish the subscription token I then edit the trigger again to remove the "test" keyword and save again. This fixed my problem and it will work for a few more months until it corrupts again. MSFT should really fix this as it creates conditions where flows fail without the owner being alerted.

Was this reply helpful? Yes No
Suggested answer

Travis- 11 on at

Like (0)

Report
Because this issue happens from time to time, I monitor my Teams channels with a separate flow that notifies the admin team that a post wasn't added to our database. This workflow has notified me every time the keyword trigger failed to pick up a new post.

When we get a new message in one of our Teams channels, it's saved to a Sharepoint list. If you do not save your post information to a database, you will need to figure out another way to verify whether you got the post in step 2.

Here's what I do. (It's really basic.)

1. Main Flow: "When keywords are mentioned" trigger, do some stuff and save the post information to a Sharepoint list.

2. Monitor Flow: "When a new channel message is added". Check to see if the post is in Sharepoint list. If not, wait a minute and check again. If it's still not there, notify admin the flow failed.

The "keyword" trigger in my organization usually fires within 30 seconds of the message being posted.

The "when a new channel message is added" trigger can take up to 3 minutes, so it already has a natural delay. If my keyword flow worked, the post will be in the Sharepoint list by the time this flow fires.

Was this reply helpful? Yes No