Error Code 403 on "When I'm @mentioned" trigger

(1) Share

Report

Posted on by KT-12060140-0 Microsoft Employee

I'm using "When I'm @mentioned" trigger in my flow but suddenly encountered the "limit of 5" error 2 days ago. I couldn't resolve this issue no matter what, so I've reset my personal dev env and recreated. However, I still encounter this issue. That chat group specified here is one of my group chat where this flow is triggered. What is it and how can I fix it?

----- ERROR -----
Error code: ExtensionError, message: Operation: Create; Exception: [Status Code: Forbidden; Reason: User 'a83bdbdf-f88b-4167-b661-c79094c3d487' has reached its limit of '5' 'CHATS/19:572068F8FE5045429BE6512B3CCBFDAB@THREAD.V2/MESSAGES' subscription on tenant '72f988bf-86f1-41af-91ab-2d7cd011db47'.], request-id: 047a41ee-b072-4eba-9904-d59d38095438, date: 6/12/2026 1:33:44 AM
------------------

ErrorCode403_12-6-2026_105235_make.powerautomate.com.jpeg

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

The error is not related to your Power Automate environment itself. It is coming from the Microsoft Teams / Microsoft Graph subscription

limit that the "When I'm @mentioned" trigger uses behind the scenes.

The most likely explanation is that your account already has five active Microsoft Graph message subscriptions associated with that

Teams chat, either from existing flows or stale/orphaned subscriptions. Until one of those subscriptions is removed or expires, Power

Automate cannot create another "When I'm @mentioned" trigger for that chat.

Start by checking for duplicate flows and testing the trigger against a different Teams chat. If the problem persists, open a Microsoft

support case and provide the full error message, as they can inspect and clean up hidden Graph subscriptions that aren't accessible

through Power Automate.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @KT-12060140-0,

your account has hit the limit of 5 Microsoft Graph message subscriptions on that specific chat thread.

The subscription limit applies per user per chat. Even after resetting your dev environment, the orphaned Graph subscriptions from deleted flows remain active until they expire (typically 60 minutes for chat subscriptions, but can be longer).

To resolve:

1. Wait: Graph subscriptions auto-expire. Chat message subscriptions expire after a maximum of 60 minutes according to Microsoft docs. If you recreated the environment recently, wait an hour and try again.

2. Delete stale flows: check all environments (including your original one) for any flows using the "When I'm @mentioned" trigger on that same chat. Deleting the flow should clean up its subscription.

3. If subscriptions are orphaned from deleted flows: you need to use the Microsoft Graph API to list and delete them manually:
- GET https://graph.microsoft.com/v1.0/subscriptions
- DELETE https://graph.microsoft.com/v1.0/subscriptions/{id}

Use Graph Explorer (https://developer.microsoft.com/graph/graph-explorer) with your account credentials to list and delete the stale subscriptions.

4. Microsoft support can also force-clean subscriptions from their side if Graph Explorer doesn't work.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No