microsoft / microsoft/BotFramework-WebChat

Time out issue with WebChat when using M365 Agent SDK

Open
#5,639 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bot Services bug customer-reported
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?

Latest production

Which distribution are you using Web Chat from?

NPM

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

No response

Which area does this issue affect?

Development experience

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

We are facing time out issue with the bot framework webchat when using M365 Agent SDK. The send and receive of the messages fail, and there are no responses. We have currently tried on the Chrome, and the Edge browsers.

When the user sends a prompt, it starts processing, but then after a couple of seconds, it dies. Not sure if the message is sent ot not, and there is no response after that. We have attached the HAR file as well as the screensh0ot for reference. Any help is highly appreciated.

QueryNetwork.har.txt

Image
Do you see any errors in console log?

How to reproduce the issue?
  1. Navigate to ...
  2. Click on ...
  3. Type "..." in the send box
What do you expect?

Its a Copilot agent that we have published on the custom webapp. We want the chatbot agent to accept user prompts and provide response normally.

What actually happened?

It seems that the message sending fails.

Do you have any screenshots or recordings to repro the issue?

No response

Adaptive Card JSON

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached QueryNetwork.har.txt and reproduce the timeout in the reported custom web app using the M365 Agent SDK. Inspect the browser network activity in Chrome or Edge to determine whether sending or receiving fails. Done means prompts are accepted and responses return normally without timing out.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.