Power Platform Community Forum Thread Details

Hello,

I am facing a very strange issue with the Microsoft Teams trigger:

"When a new message is added to a chat or channel"

The trigger worked correctly in the past and some older flows are still running successfully. However, any NEW flow created with this trigger fails immediately.

What I tested:

- Created a brand new flow containing only:

- Trigger: When a new message is added to a chat or channel

- Action: Compose

- Created new Microsoft Teams connections

- Tested different Teams and Channels

- Tested multiple Power Platform Developer environments

- Created a completely new environment

- Verified licenses and permissions

- Verified that the service account can access Teams and the channels normally

- Manual flows execute successfully

Error observed:

```json

{

"error": {

"code": 404,

"message": "Subscription Id(s) are not found. Please try updating the trigger and re-saving the flow to trigger new subscription creations"

}

Sometimes the trigger also returns:

{

"error": {

"code": 503,

"message": "Error code: ExtensionError, message: Operation: Create; Exception: [A task was canceled.]"

}

Important findings:

Existing old flows using the same Teams trigger still work.

Newly created flows fail.

The issue was reproduced in multiple environments.

Recreating the trigger, connection, and environment did not solve the problem.

This makes me think there may be a problem creating new Microsoft Graph subscriptions for the Teams trigger.

Has anyone experienced this recently or found a workaround?

Thank you.

Categories:

Using connectors

Hi,

This sounds very similar to a Microsoft Teams trigger subscription issue rather than a problem with your flow design.
The key clue is that:

Existing flows continue to work.
Newly created flows fail immediately.
The error references missing Subscription IDs and subscription creation failures.

That suggests Power Automate is unable to create the underlying Microsoft Graph subscription required by the "When a new message is added to a chat or channel" trigger.
A few things to try:

Open the trigger, make a small change, save, then revert and save again to force subscription recreation.
Create a new Teams connection under a different user account and test.
Check whether the affected environments are in the same region, as a regional service issue can impact trigger provisioning.
Review the flow's Trigger History and connection details for additional Graph-related errors.
If all new flows fail across multiple environments while existing subscriptions continue to run, open a Microsoft support ticket with the 404 and 503 error details.

Based on your testing, this does not look like a permissions or licensing issue. It appears more likely that new Graph webhook subscriptions are failing to be created, while older subscriptions remain active and continue to function.

Thanks & Regards,

Manoj Annavajjala