microsoft / microsoft/Agent365-Samples
langchain node.js sample didn't work from MS Teams
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 108
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Description
Hi, I followed Quickstart: Set up and run the JavaScript LangChain sample agent and also setup blueprint, published with local setup and also configured the MS Teams dev center for blueprint. The local agent can also be tested successfully from Playground with dev-tunnel configured. after I created an agent instance and chat the agent from MS Teams, my agent endpoint hosted on local via dev-tunnel was able to receive agent lifecycle notification and an email message. however, when I type "hello" in the chat, my agent endpoint wasn't hit. can anyone tell me how I am able to troubleshooting what problems behind?
another thing I notice is when I called context.sendActivity() for agent lifecycle notification or typing message, I got 404 ERR_BAD_REQUEST issue.
Expected behavior
the agent endpoint should receive the message.
SDK Version
0.1.0-preview.30
Language/Runtime
node.js v22.18.0
OS
Windows 11
How to Reproduce
- followed Quickstart: Set up and run the JavaScript LangChain sample agent to setup source code
- create blueprint via running "o365 config init" and "a365 setup all"
- publish without deploying "a365 publish"
- config in MS Teams dev center.
- request instance
- create instance
- type "hello" in MS Teams with that agent. got no response.
Output
No response
Screenshots
No response
Code of Conduct
- I agree to follow the Microsoft Open Source Code of Conduct.
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
Start by rerunning the linked Quickstart: Set up and run the JavaScript LangChain sample agent and inspect the local agent endpoint logs while sending "hello" from MS Teams. Compare the lifecycle notification and message requests, including the 404 from context.sendActivity(); done means the chat message reaches the endpoint and the response is delivered without a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100