openclaw - 💡(How to fix) Fix [Bug]: MSTeams "channel unresolved" error [2 comments, 3 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#74683Fetched 2026-04-30 06:21:19
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
2
Timeline (top)
commented ×2labeled ×2closed ×1mentioned ×1

I have my MS Teams team and channel IDs configured as the docs say here: https://docs.openclaw.ai/channels/msteams#team-and-channel-ids-common-gotcha

Yet when the gateway starts, I see the log message:

 [msteams] channels unresolved: 19:[email protected]/19:[email protected]

My IDs end in thread.skype instead of thread.tacv2 like the examples in the docs. I've tried changing the postfixes but didn't change anything. Also, this doesn't seem to be preventing the bot from responding in the channel.

I've observed this on every version since at least 4.23, probably before that too

Root Cause

I have my MS Teams team and channel IDs configured as the docs say here: https://docs.openclaw.ai/channels/msteams#team-and-channel-ids-common-gotcha

Yet when the gateway starts, I see the log message:

 [msteams] channels unresolved: 19:[email protected]/19:[email protected]

My IDs end in thread.skype instead of thread.tacv2 like the examples in the docs. I've tried changing the postfixes but didn't change anything. Also, this doesn't seem to be preventing the bot from responding in the channel.

I've observed this on every version since at least 4.23, probably before that too

Code Example

[msteams] channels unresolved: 19:4b6...@thread.skype/19:d2e...@thread.skype

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

I have my MS Teams team and channel IDs configured as the docs say here: https://docs.openclaw.ai/channels/msteams#team-and-channel-ids-common-gotcha

Yet when the gateway starts, I see the log message:

 [msteams] channels unresolved: 19:[email protected]/19:[email protected]

My IDs end in thread.skype instead of thread.tacv2 like the examples in the docs. I've tried changing the postfixes but didn't change anything. Also, this doesn't seem to be preventing the bot from responding in the channel.

I've observed this on every version since at least 4.23, probably before that too

Steps to reproduce

Configure MS Teams team and channel ID as shown in docs, start gateway, observe log about unresolved channels

Expected behavior

No log entry

Actual behavior

Log shows 'channels unresolved'

OpenClaw version

2026.4.27

Operating system

Ubuntu 24.04.4 LTS

Install method

npm global

Model

NA

Provider / routing chain

NA

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 issue might be related to the MS Teams team and channel ID configuration, specifically the postfix used, but it does not seem to affect the bot's functionality.

Guidance

  • Verify that the team and channel IDs are correctly formatted according to the documentation, focusing on the postfix (thread.skype vs thread.tacv2).
  • Check if the log message about unresolved channels is merely informational and does not impact the bot's ability to respond in the channel, as indicated by the user's observation.
  • Investigate if there are any version-specific changes or updates in the OpenClaw documentation or MS Teams API that could affect the ID format or the logging behavior.
  • Consider reaching out to the OpenClaw support or community to clarify the purpose of the log message and whether it indicates an actual issue.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The issue does not seem to prevent the bot from functioning correctly, but it's unclear if the log message indicates a potential problem that could arise in the future or under different circumstances.

Recommendation

Apply workaround: Since the bot appears to be functioning despite the log message, and given that changing the postfix did not resolve the issue, it might be best to monitor the situation and seek further clarification from OpenClaw support rather than taking immediate action that could potentially disrupt the current functionality.

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

No log entry

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: MSTeams "channel unresolved" error [2 comments, 3 participants]