Teams trigger 'When a new message is added to a channel' returns UnknownError for specific channel

(0) Share

Report

Posted on by 行桑-03100413-0

I am encountering an issue with a Power Automate flow that uses the trigger "When a new message is added to a channel" (Microsoft Teams).

The flow works correctly for most channels across various teams. However, when configured to monitor a specific channel within a particular team, it consistently fails with the following error:

{
  "statusCode": 400,
  "error": {
    "code": "BadRequest",
    "message": "UnknownError",
    "innerError": {
      "request-id": "907d4c62-2aa3-4043-bf5a-891a8356876f",
      "client-request-id": "907d4c62-2aa3-4043-bf5a-891a8356876f"
    }
  }
}

I have verified the following:

The Microsoft Teams connection is active and authenticated.

The team and channel are correctly selected and exist.

The channel is a standard channel (not private or shared).

The user creating the flow is a member of the team.

Other channels within the same team work without issues using the same trigger

Despite these checks, the error persists only for this specific channel. I would appreciate your assistance in identifying the cause and resolving the issue.

Please let me know if you require any additional information or logs.

Best regards,

Categories:

Building flows

I have the same question (10)

All responses (8)

Answers (0)

developerAJ 4,763 on at

Like (1)

Report
Copy link

Link copied!

Hi

Are you receiving this error on Trigger or an action configured in the flow

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

行桑-03100413-0 10 on at

Like (1)

Report
Copy link

Link copied!

@developerAJ
Thanks for your reply. The error occurs at the trigger level — "When a new message is added to a channel". The flow does not proceed beyond this point. Other channels work fine with the same trigger.

Was this reply helpful? Yes No
CU03101825-0 6 on at

Like (2)

Report
Copy link

Link copied!

any suggestions? I'm experiencing this as well oddly today

Was this reply helpful? Yes No
wwade 6 on at

Like (2)

Report
Copy link

Link copied!

Experiencing the same issue as well, starting sometime between October 1st at 3:07 PM and October 2nd at 8:13 AM based on when I would have expected the flow to trigger.

Was this reply helpful? Yes No
Suggested answer

developerAJ 4,763 on at

Like (1)

Report
Copy link

Link copied!

Is it possible to share the body to help debug the issue?

However, we won’t be able to fix it, as it’s happening with the trigger. Please log a ticket with Microsoft for this. I’ve checked the service health in my tenant and don’t see any such issue.

If this solution helped you resolve your issue, kindly mark it as accepted — it makes it easier for others to find and also closes the discussion. If you found it useful, a Like ❤️ would be greatly appreciated!

🤝 Let’s connect on LinkedIn || 📘 Explore more on my articles

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

行桑-03100413-0 10 on at

Like (0)

Report
Copy link

Link copied!

After checking again at the beginning of the week, the trigger issue had been resolved.

Therefore, I’ll mark your response as “Accepted.”

Thank you for your support!

Was this reply helpful? Yes No
AG-02101444-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi, I'm also having the exact same problem since last Thursday. I have around 8 flows that are the same for different channels. One of them has worked fine the whole time with no errors or delays, two of them randomly pulled data at different points on Friday, and one pulled all the missing data through this morning at 1:36am. However still have 4 that are saying there's a problem with the trigger due to error 429 "too many requests". The alert also says "Your operation has been throttled. Looks like your flow's operation is hitting an action limit designed to protect the connector service being called." But can't figure out why this is happening.

Was this reply helpful? Yes No
developerAJ 4,763 on at

Like (0)

Report
Copy link

Link copied!

Please let us know if the issue still exists. If it has been resolved, kindly close the thread by accepting the solution

If this solution helped you resolve your issue, kindly mark it as accepted — it makes it easier for others to find and also closes the discussion. If you found it useful, a Like ❤️ would be greatly appreciated!

🏷️ Please tag me @developerAJ if you still have any queries or issue persists.

🤝 Let’s connect on LinkedIn

📘 Explore more on my articles

🐱‍💻 Github Link

Was this reply helpful? Yes No