search

microsoft / BotFramework-Services

Microsoft Bot Framework Services
Creative Commons Attribution 4.0 International
38 stars 11 forks source link

Reconnect to a conversation in Direct Line API 3.0 #319

Closed mmiele closed 2 years ago

mmiele commented 2 years ago

Following the user’s intent as described in the issue: Generate a new WebSocket stream URL #2050, it sounds like the reconnect endpoint is returning the full conversation history regardless of if the ‘Watermark’ parameter is sent or not. Reading the article Reconnect to a conversation in Direct Line API 3.0, assuming that it’s correct, it seems that this is a bug. From the documentation point of view, we need to know if the current behavior is by design and some explanation for the customer. Please advice.

JonathanFingold commented 2 years ago

@MichaelHaydenAtMicrosoft

craigjensen commented 2 years ago

@mmiele Please attach a conversationId and approx timestamp and I'll see if I can figure out where the issue is.

mmiele commented 2 years ago

@mmiele Please attach a conversationId and approx timestamp and I'll see if I can figure out where the issue is.

This is the doc issue opened by the customer: https://github.com/MicrosoftDocs/bot-docs/issues/2050

JonathanFingold commented 2 years ago

@craigjensen please follow up with https://github.com/Mohammed-Ahmed-Ismail for more information.

craigjensen commented 2 years ago

@Mohammed-Ahmed-Ismail Please attach a conversationId and approx timestamp and I'll see if I can figure out where the issue is.

MichaelHaydenAtMicrosoft commented 2 years ago

@Mohammed-Ahmed-Ismail, are you able to attach a conversationid and timestamp? We will need to this in order to troubleshoot further.

MichaelHaydenAtMicrosoft commented 2 years ago

Closing for now. We tested on our end and bot is responding. Please re-open if issue reoccurs