Answered

The flow to post to Teams chat (triggered by Power Apps) fails.

(0) Share

Report

Posted on by Fuku-shima-

Calling flows from Power Apps has been failing since 3/16. Please let me know the solution and information about the failure.

(1) What I'm trying to do.
I want to call a flow that executes "Post a message as the Flow bot to a user" triggered by Power Apps by pressing a button on the app.

(2) The problem that happened
This flow used to work as intended. However, since around March 11, when someone other than the creator of the flow executes it, it does not work properly anymore. When it fails, there are two patterns as follows.
・The error ""code": "AuthorizationFailed"" occurs in "Post a message as the Flow bot to a user" and the flow execution fails.
・The flow invocation process (Run function) fails on the application side.The app is using IsError(Run(,,,,)), but it may not be able to catch the error even though the call is not made (not shown in the flow execution history).

I suspected that it was due to the Azure AD failure that occurred on March 16, but this symptom has not been resolved even now that Azure AD has been restored. (I was able to run it temporarily right after Azure AD was restored.)

(3) What I have checked
We have confirmed that the user account that is experiencing this issue is able to use Power Automate and Teams, and that the Teams connector is in the connected status.

Please let me know any failure information or solutions regarding this issue.
If I have posted the question in the wrong Location, I would appreciate it if you could tell me the correct Location.

Thanks in advance.

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (1)

Sort by

annajhaveri 8,531 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@Fuku-shima- can you provide the exact error that you are getting or the failed flow run screenshot?

Was this reply helpful? Yes No
Fuku-shima- 7 on at

Like
a
(0)

Report
Copy link

Link copied!
@annajhaveri
Thank you for your reply.
For some reason this post keeps disappearing, so I'm reposting it. Sorry for notifying you so many times.
(1) In the case that the flow is successfully invoked but the Teams action fails
The error output for the "Post a message as the Flow bot to a user" action is shown below.
I have replaced the ID with "XXXX".
Please note that the error messages may be different from those in English-speaking countries because of the Japanese environment.

{ "statusCode": 401, "headers": { "Pragma": "no-cache", "x-ms-request-id": "japaneast:XXXX", "x-ms-correlation-request-id": "XXXX", "x-ms-flow-mobile-ios-version": "1.3.0", "x-ms-flow-routing-request-id": "JAPANEAST:20210317T074120Z:XXXX", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "X-Content-Type-Options": "nosniff", "Timing-Allow-Origin": "*", "x-ms-apihub-cached-response": "false", "Cache-Control": "no-cache", "Date": "Wed, 17 Mar 2021 07:41:19 GMT", "Content-Length": "174", "Content-Type": "application/json", "Expires": "-1" }, "body": { "error": { "code": "AuthorizationFailed", "message": "クライアント証明書または Authorization ヘッダーが指定されていません。" } } }

(2) In the case where the flow call fails from the application
The call has failed, so it is not in the execution history of the flow.
If the below syntax is used, an "Error" will be displayed on the app screen.
"If(IsError(Run(,,,)),Notify("Error"),Notify("Success"))"

Was this reply helpful? Yes No
Verified answer

annajhaveri 8,531 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

@Fuku-shima- have there been any network configuration changes in your organization, that could be stripping authentication header from request, from error it looks like authentication issue.

Was this reply helpful? Yes No
Fuku-shima- 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for your reply.
It seems that the problem was caused by a combination of factors (our environment and Azure AD's failure).
I was able to resolve the issue by re-adding the flow to the app and re-authenticating the user's account.
I apologize for the delay in replying.
Thank you very much for your help.

Was this reply helpful? Yes No