openclaw - 💡(How to fix) Fix [Bug]: Microsoft Teams Asymmetrical communication [4 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73167Fetched 2026-04-29 06:22:42
View on GitHub
Comments
4
Participants
4
Timeline
10
Reactions
0
Assignees
Timeline (top)
commented ×4labeled ×2assigned ×1closed ×1

Microsoft Teams inbound messages stopped reaching OpenClaw after upgrading from 2026.4.9 to 2026.4.25/2026.4.26.

Outbound Teams sending still works, and Discord still works both directions. Downgrading to 2026.4.9 restores Teams replies.

Root Cause

Additional notes

This looks like a Teams inbound webhook/listener regression because there is no OpenClaw log movement when messages are sent, while outbound Teams sending still works.

Fix Action

Fix / Workaround

Reproduction steps

  1. Run OpenClaw 2026.4.9 with Microsoft Teams configured.
  2. Send a Teams DM or @mention the bot in a Teams group chat.
  3. Confirm the agent replies.
  4. Upgrade to OpenClaw 2026.4.26.
  5. Send the same Teams DM or group @mention.
  6. Observe no reply and no new OpenClaw log movement.
  7. Downgrade to 2026.4.9.
  8. Observe Teams replies working again.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Microsoft Teams inbound messages stopped reaching OpenClaw after upgrading from 2026.4.9 to 2026.4.25/2026.4.26.

Outbound Teams sending still works, and Discord still works both directions. Downgrading to 2026.4.9 restores Teams replies.

Steps to reproduce

Reproduction steps

  1. Run OpenClaw 2026.4.9 with Microsoft Teams configured.
  2. Send a Teams DM or @mention the bot in a Teams group chat.
  3. Confirm the agent replies.
  4. Upgrade to OpenClaw 2026.4.26.
  5. Send the same Teams DM or group @mention.
  6. Observe no reply and no new OpenClaw log movement.
  7. Downgrade to 2026.4.9.
  8. Observe Teams replies working again.

Expected behavior

Teams DMs and @mentioned group messages should be received by OpenClaw and routed to the agent.

Actual behavior

Teams messages appear to never reach OpenClaw inbound handling/logging on 2026.4.25/2026.4.26.

OpenClaw version

  • Broken: OpenClaw 2026.4.25 and 2026.4.26

Operating system

ubuntu 24

Install method

npm

Model

minimax

Provider / routing chain

minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Additional notes

This looks like a Teams inbound webhook/listener regression because there is no OpenClaw log movement when messages are sent, while outbound Teams sending still works.

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.9 to restore Microsoft Teams inbound message functionality.

Guidance

  • Verify that the issue is specific to Microsoft Teams inbound messages by checking that outbound Teams sending and Discord integration are working as expected.
  • Review the OpenClaw changelog for versions 2026.4.25 and 2026.4.26 to identify potential changes that may have caused the regression.
  • Test the inbound message functionality with different Microsoft Teams configurations to determine if the issue is specific to a particular setup.
  • Consider reporting the issue to the OpenClaw development team to request a fix for the regression in a future version.

Example

No code snippet is provided as the issue does not require a code-level fix, but rather a version downgrade.

Notes

The provided information suggests that the issue is specific to OpenClaw versions 2026.4.25 and 2026.4.26, and downgrading to version 2026.4.9 resolves the issue. However, this may not be a long-term solution, and a fix for the regression should be requested from the OpenClaw development team.

Recommendation

Apply workaround: Downgrade to OpenClaw version 2026.4.9, as it is the only known version that resolves the Microsoft Teams inbound message regression.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Teams DMs and @mentioned group messages should be received by OpenClaw and routed to the agent.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING