Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: blockStreaming not supported for msteams channel [1 comments, 2 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#69712•Fetched 2026-04-22 07:49:08
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Sayujaya14Sayujaya14
Participants
rafiki270rafiki270Sayujaya14Sayujaya14
Timeline (top)
labeled ×2commented ×1

Description: The blockStreaming: true config key works on WhatsApp but is not recognized for the msteams channel. Setting it manually in openclaw.json causes gateway validation failure, and openclaw config set channels.msteams.blockStreaming true returns: Config validation failed: channels.msteams: Unrecognized key: "blockStreaming"

Error Message

  1. Attempt to restart the gateway — gateway fails to start with a validation error
  2. Direct file edit → gateway throws a validation error and cannot restart

Root Cause

Description: The blockStreaming: true config key works on WhatsApp but is not recognized for the msteams channel. Setting it manually in openclaw.json causes gateway validation failure, and openclaw config set channels.msteams.blockStreaming true returns: Config validation failed: channels.msteams: Unrecognized key: "blockStreaming"

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Description: The blockStreaming: true config key works on WhatsApp but is not recognized for the msteams channel. Setting it manually in openclaw.json causes gateway validation failure, and openclaw config set channels.msteams.blockStreaming true returns: Config validation failed: channels.msteams: Unrecognized key: "blockStreaming"

Steps to reproduce

  1. Open openclaw.json and add "blockStreaming": true under channels.msteams
  2. Attempt to restart the gateway — gateway fails to start with a validation error
  3. Alternatively, run: openclaw config set channels.msteams.blockStreaming true

Expected behavior

Teams should support blockStreaming: true the same way WhatsApp does, to prevent the streaming/typing indicator double-bubble in Teams DMs.

Actual behavior

  1. Direct file edit → gateway throws a validation error and cannot restart
  2. CLI command → returns: Config validation failed: channels.msteams: Unrecognized key: "blockStreaming"
  3. The same key works fine on channels.whatsapp without any errors

OpenClaw version

2026.3.24

Operating system

Ubuntu 24

Install method

docker

Model

antropic/claude/sonnet 4-5

Provider / routing chain

Anthropic (Claude)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The blockStreaming config key is not recognized for the msteams channel, causing a validation error when set manually or through the CLI.

Guidance

  • Verify that the blockStreaming key is supported for the msteams channel in the OpenClaw documentation or release notes.
  • Check if there are any channel-specific configuration options or workarounds for msteams that can achieve the desired behavior.
  • Consider filing a feature request or bug report with OpenClaw to add support for blockStreaming on the msteams channel.
  • If the blockStreaming key is not essential, remove it from the msteams configuration to allow the gateway to start.

Example

No code snippet is provided as the issue is related to configuration and not code.

Notes

The blockStreaming key works for the whatsapp channel, but not for msteams, indicating a potential channel-specific configuration issue.

Recommendation

Apply workaround: Remove the blockStreaming key from the msteams configuration to allow the gateway to start, and consider filing a feature request to add support for this key on the msteams channel.

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 should support blockStreaming: true the same way WhatsApp does, to prevent the streaming/typing indicator double-bubble in Teams DMs.

#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING