microsoft / microsoft/BotFramework-WebChat
Timed out while waiting for activity
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is it an issue related to Adaptive Cards?
No
Is this an accessibility issue?
No
What version of Web Chat are you using?
I am not using latest
Which distribution are you using Web Chat from?
Bundle (webchat.js)
Which hosting environment does this issue primarily affect?
Web apps
Which browsers and platforms do the issue happened?
Browser: Chrome (latest)
Which area does this issue affect?
Chat history
Which theme pack does this issue affect?
I did not test it on other theme packs
What is the public URL for the website?
No response
Please describe the bug
I would like to follow-up this issue, which should be resolved. However, I sill get this error with the latest version v4.18. Can you check this? Thanks
Do you see any errors in console log?
botframework-webchat: Timed out while waiting for activity "2677ac02-c9ff-47a2-b140-d5af9cc7ad9e" which activity "fc025a2a-3f35-4241-b024-0d95285920eb" is replying to.
How to reproduce the issue?
- Follow the setup from: https://github.com/microsoft/Agents/tree/main/samples/nodejs/copilotstudio-webclient
- Fill Copilot credentials
- Send any message and watch the Console
What do you expect?
There should be no timeout
What actually happened?
When connecting to Copilot, even though Copilot responded successfully, it only displayed the response after the timeout.
Do you have any screenshots or recordings to repro the issue?
No response
Adaptive Card JSON
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the microsoft/Agents samples/nodejs/copilotstudio-webclient setup in Chrome with the Copilot credentials, then trace the console timeout involving the two activity IDs. Confirm why the response is displayed only after the timeout and verify that a normal Copilot reply appears without the timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100