Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: MS Teams bot can no longer send files after updating to OpenClaw 2026.4.2 [1 pull requests, 2 comments, 1 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#60003•Fetched 2026-04-08 02:37:37
View on GitHub
Comments
2
Participants
1
Timeline
8
Reactions
0
Author
juanchighionejuanchighione
Participants
juanchighionejuanchighione
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1

After updating OpenClaw to 2026.4.2 (d74a122), my Microsoft Teams bot stopped being able to send files/attachments.

Before this update, sending files from the bot in Teams was working correctly.

The bot still works for normal text messages. This started immediately after updating to OpenClaw 2026.4.2. with openclaw 2026.3.8 (b6520d7) works.

Root Cause

After updating OpenClaw to 2026.4.2 (d74a122), my Microsoft Teams bot stopped being able to send files/attachments.

Before this update, sending files from the bot in Teams was working correctly.

The bot still works for normal text messages. This started immediately after updating to OpenClaw 2026.4.2. with openclaw 2026.3.8 (b6520d7) works.

Fix Action

Fixed

PR fix notes

PR #60022: fix: restore MS Teams file sending functionality

Description (problem / solution / changelog)

Summary

Restores the ability for MS Teams bots to send files/attachments, which was broken in v2026.4.2.

Changes

  • Fixes isImage evaluation in the reply dispatcher by relying on contentType rather than media.kind which is undefined for attachments, allowing fallbacks or base64 to correctly execute.
  • Restores the AI_GENERATED_ENTITY correctly across Teams proactive file activities, adaptive cards, and consent cards preventing 400 Bad Request drops by the native Teams client.
  • Adds a token guard inside sendMessageMSTeams so that OneDrive fallback explicitly rejects if tokenProvider is missing.

Testing

  • Verified Teams file upload logic

Fixes openclaw/openclaw#60003

Changed files

  • extensions/msteams/src/messenger.ts (modified, +4/-1)
  • extensions/msteams/src/send.ts (modified, +11/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After updating OpenClaw to 2026.4.2 (d74a122), my Microsoft Teams bot stopped being able to send files/attachments.

Before this update, sending files from the bot in Teams was working correctly.

The bot still works for normal text messages. This started immediately after updating to OpenClaw 2026.4.2. with openclaw 2026.3.8 (b6520d7) works.

Steps to reproduce

NOT_ENOUGH_INFO

Expected behavior

The bot should be able to send files in Teams, as it did before the update.

Actual behavior

After updating OpenClaw to 2026.4.2 (d74a122), my Microsoft Teams bot stopped being able to send files/attachments.

OpenClaw version

2026.4.2 (d74a122)

Operating system

ubuntu 24.04

Install method

bmp global

Model

gpt 5.1 codex

Provider / routing chain

Microsoft Teams -> ngrok -> self-hosted OpenClaw gateway

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade OpenClaw to version 2026.3.8 (b6520d7) to potentially resolve the issue with sending files/attachments from the Microsoft Teams bot.

Guidance

  • Verify that the issue is specific to OpenClaw version 2026.4.2 by testing with a previous version, such as 2026.3.8, which is known to work.
  • Check the release notes for OpenClaw 2026.4.2 to see if there are any known issues or changes related to file sending or attachments.
  • Test the bot with a different provider or routing chain to determine if the issue is specific to Microsoft Teams or the ngrok setup.
  • Consider reaching out to the OpenClaw community or support team for further assistance, as the issue may be related to a bug or regression in the new version.

Notes

The lack of detailed logs, screenshots, and evidence makes it difficult to provide a more specific solution. Additionally, the "NOT_ENOUGH_INFO" in the steps to reproduce section limits the ability to provide a comprehensive fix.

Recommendation

Apply workaround: Downgrade to OpenClaw version 2026.3.8 (b6520d7), as it is known to work correctly for sending files/attachments from the Microsoft Teams bot. This is a temporary solution until the issue with version 2026.4.2 can be resolved.

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

The bot should be able to send files in Teams, as it did before the update.

#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING