Not receiving both conversation id and service url for an activity (via Teams)

[AKSHILMY]

Hi there,
I observed that sometime I do not get the conversation id or the service url id for the activity and I am unable to proceed the conversation. I am unable to reproduce the issue.
I would like to know the possibilities of such an issue occurring ? I am able to get the aad_id from the activity , so I would like to know whether there is a possibility to get the conversation id or the service url using the aad id?

[stevkan]

I suspect this is a Teams issue and not an SDK issue. But let's do a little information gathering on this, first.

• What kind of bot is this? SDK (code-first), Composer, or a PVA/Copilot bot?
• If SDK or Composer, what language was used and which version of the SDK / app?
• Is there a pattern attributable to this? Do you notice this on certain kinds of activities only or following certain conversation flows, prompts, etc.?
• Does this happen only when the bot is deployed? Have you tested for this with a bot running locally?
• What kind of error is being returned? Is there anything being reported in the developer's console or in logging anywhere (server logs, application insights, etc.)?

[AKSHILMY]

• SDK (code-first)
• Python , SDK version : 4.14.4
• No pattern observed
• Observed in deployment (When testing locally using the Bot Framework emulator, I observed that when I change some tunnel configuration when tried to use ngrok, the payload sent to back end appears to be missing conversation id and service url and some other)