TLDR ...
We Think we have found a timing bug.
Roughly 20% of the time, on adding app (bot) to chat (group call/meeting), the bot is conected to the message feed AFTER the MemeberAdded event is sent to the feed. So the bot does not receive the onMembersAdded event.
We have a combined bot (node.js) / tab (react) app deployed on several of our client's tenants.
This app is specifically for online meetings (Group calls) not 1-2-1 ot channel.
The bot is configured to receive event messages from the 'teams channel' as part of the bot configuration in azure > bot > settings > Channels, with the endpoint URL configured in bot > settings > configuration.
The bot, amongst other things send chat messages and targetted notifications using ConversationReferenceJSON.
Historically our bot has acquired the conversationReferenceJSON using the activity sent with the onMembersAdded message/event sent to the configured (Channel) messages endpoint URL.
Recently we have noticed this has become unreliable ...
We are still seeing 100% success from our own tenant, our development tenant and some client tenants.
However we are seeing up to 70% failure rate from some client tenants (possibly the busier tenants - although this is a guess).
FWIW : Where tenant have a high failure rate it is still intermittent so we do not believe it is a configuration issue.
When we have tracked back through logs / db this seems to have started in late October 2025, and steadily become more common, failing 51 times across 161 meetings since then.
When we add an app to chat (for the meeting) 2 (relevant) things happen in the background :
(1) this meeting is hooked up to the 'teams messages' channel (as per bot config) for this meeting/call/chat
(2) an onMembersAdded event is fired on the 'teams messages' channel for this meeting/call/chat - saying the bot has been added
What we perceive is happening (inside the black box) when our setup fails :
We think that the 2 events must be async and that when it 'fails' it is that the onMemberAdded event is fired before the chat in question is added to the teams channel message feed for our bot.
Possible fix - make the channel hook up synchronous so that it is completed before triggered events are sent ?
I believe we build this code structure based on various MS examples for teams notification bots - so would have expected this to work consistently
Please can someone review this
TIA,
PugeLaRouge
TLDR ...
We Think we have found a timing bug.
Roughly 20% of the time, on adding app (bot) to chat (group call/meeting), the bot is conected to the message feed AFTER the MemeberAdded event is sent to the feed. So the bot does not receive the onMembersAdded event.
We have a combined bot (node.js) / tab (react) app deployed on several of our client's tenants.
This app is specifically for online meetings (Group calls) not 1-2-1 ot channel.
The bot is configured to receive event messages from the 'teams channel' as part of the bot configuration in azure > bot > settings > Channels, with the endpoint URL configured in bot > settings > configuration.
The bot, amongst other things send chat messages and targetted notifications using ConversationReferenceJSON.
Historically our bot has acquired the conversationReferenceJSON using the activity sent with the onMembersAdded message/event sent to the configured (Channel) messages endpoint URL.
Recently we have noticed this has become unreliable ...
We are still seeing 100% success from our own tenant, our development tenant and some client tenants.
However we are seeing up to 70% failure rate from some client tenants (possibly the busier tenants - although this is a guess).
FWIW : Where tenant have a high failure rate it is still intermittent so we do not believe it is a configuration issue.
When we have tracked back through logs / db this seems to have started in late October 2025, and steadily become more common, failing 51 times across 161 meetings since then.
When we add an app to chat (for the meeting) 2 (relevant) things happen in the background :
(1) this meeting is hooked up to the 'teams messages' channel (as per bot config) for this meeting/call/chat
(2) an onMembersAdded event is fired on the 'teams messages' channel for this meeting/call/chat - saying the bot has been added
What we perceive is happening (inside the black box) when our setup fails :
We think that the 2 events must be async and that when it 'fails' it is that the onMemberAdded event is fired before the chat in question is added to the teams channel message feed for our bot.
Possible fix - make the channel hook up synchronous so that it is completed before triggered events are sent ?
I believe we build this code structure based on various MS examples for teams notification bots - so would have expected this to work consistently
Please can someone review this
TIA,
PugeLaRouge