Directline Reconnect Issue
See original GitHub issueProblem
- Directline sending all past activity when connecting to an old conversation
Issue Description
Reconnecting to old conversation relies on Reconnect Conversation API. Microsoft API is currently having an issue where they are always returning watermark=-
in API
We found the issue in directline when we tried to resolve this issue with Directline APIs.
I could not find place to register issue to directline api. So, if it relates to any internal repository for direcltine kindly forward this issue to right place.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Reconnect to a conversation in Direct Line API 3.0
In this scenario, the client must generate a new WebSocket stream URL that it can use to reconnect to the conversation.
Read more >node.js - How to reconnect WebChat to old conversation with ...
In this scenario, you will setup a token server to make the Direct Line API calls when your own server endpoints are contacted....
Read more >asksuite-botframework-directlinejs - npm
Calling the DirectLine reconnect API yourself to get a refreshed token and a streamurl; Creating the DirectLine object using the ConversationId, ...
Read more >Direct Line Web Client - Microsoft Open Source
The Direct Line Web Client client lets you chat with any Virtual Assistant that has Direct Line or Direct Line Speech enabled from...
Read more >botframework-directlinejs | Yarn - Package Manager
Resume an existing conversation · Storing the conversationid and your token (in a permanent place, like local storage) · Calling the DirectLine reconnect...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a regression in the directline service. The fix will go out with this week’s release
We had the same issue today, we removed the dash after the
watermark=
as a quick fix