-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Response timeouts with DirectLineSpeech #3773
Copy link
Copy link
Closed
Labels
Bot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.bugIndicates an unexpected problem or an unintended behavior.Indicates an unexpected problem or an unintended behavior.customer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.
Metadata
Metadata
Assignees
Labels
Bot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.Required for internal Azure reporting. Do not delete. Do not change color.bugIndicates an unexpected problem or an unintended behavior.Indicates an unexpected problem or an unintended behavior.customer-replied-toRequired for internal reporting. Do not delete.Required for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.Required for internal Azure reporting. Do not delete.
Screenshots
Version
NPM:
botframework-webchat": "^4.11.0Describe the bug
After connecting a bot with DirectLineSpeech, every activity (except of the first one), no matter if text or speech, receive timeout while waiting for reply. In other platforms (emulator, postman, azure portal emulator) there is no timeout and all the responses are quick.
Steps to reproduce
Expected behavior
The response should be quick like the first response
Additional context
None
[Bug]