The workflow in Power Apps didn't work as expected.

(0) Share

Report

Posted on by ZW-22060612-0

We are using a flow to send notifications to stakeholders, and it was working fine until last Thursday. However, it has recently stopped working as expected.
Specifically, the trigger in the first step is now returning a 400 Bad Request error, without providing any useful logs. The trigger type is OpenApiConnection, and the definition is provided below. The values of the groupId and channelId is correct.

We have not made any changes to the configuration. I also tried creating and using a new connection under my account, but the issue still persists.
Additionally, my account is the owner of the corresponding Teams, so permission issues are unlikely.
I also tried to retrieve additional logs from the Power Platform Admin Center, but no relevant entries could be found.
Could anyone please help look into this issue? Many thanks in advance.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @ZW-22060612-0,

Initially seems like a service disruption issue. Can you please quickly do test with a minmal flow - a simple flow with the same trigger and parameters to isolate the issue?

Other two options you can have:

Re-save the flow: Edit the flow trigger and save it again to force re-registration.

Recreate the trigger: Delete and add the trigger anew in the flow.

Note: Connector or API changes: Updates on the Teams connector or Microsoft Graph API can cause triggers to fail unexpectedly. Also, you can Review throttling: If you have many flows or frequent triggers, consider spreading out runs or adding retry policies.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
ZW-22060612-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Haque,

Thanks for your reply. I’ve tried the suggestions you mentioned, including recreating the connection, creating a new sample trigger with a sample action, and re‑saving the flow.
However, the trigger has been skipped since I updated the connection without any error/warning message. I’m confident that there is no permission issue with my connection, as it can successfully retrieve data from the corresponding channel in another test flow.
At the moment, all flows that use OpenApiConnection as the trigger type with OnNewChannelMessage as the operationId cannot be triggered successfully. I’m not sure how to proceed with fixing this issue...

B.R.
Ziyang

Was this reply helpful? Yes No