solution channel high macos linux windows signal

Signal: group sends fail ('Group not found') due to case-sensitive group IDs

Fix Signal group targeting failures by preserving the exact group ID casing and upgrading if your version lowercases base64 IDs.

By CoClaw Team •

Symptoms

  • Proactive sends to a Signal group fail with “Group not found”.
  • DMs work, and replying inside the group can still work, but scripted sends (CLI/tool/cron) to the group fail.

Cause

Signal group IDs are base64 and case-sensitive. Some versions or tooling can accidentally lowercase the group id, which breaks targeting.

Fix

1) Copy the group id exactly (preserve casing)

When you store or paste a group id, keep it exactly as provided by OpenClaw / signal-cli (do not lowercase it).

2) Prefer replying in-thread while you recover

If you can still reply to a message inside the group, do that first (the session already knows the correct group id).

3) Upgrade OpenClaw if you suspect an old normalization bug

If your version lowercases group IDs, upgrade OpenClaw to the latest version and restart the gateway.

Verify

  • A test send to signal:group:<groupId> succeeds.
  • The group receives the message.

Verification & references

  • Reviewed by:CoClaw Code Team
  • Last reviewed:March 14, 2026
  • Verified on: macOS · Linux · Windows

References

Official docs

  1. OpenClaw docs: /channels/signal

Issue threads

  1. OpenClaw GitHub issue #7354
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

Signal: signal-cli not found / daemon won't start
Fix
Fix Signal channel startup by installing signal-cli + Java, setting cliPath, and increasing startup timeout or using an external daemon (httpUrl).
Feishu: TTS voice replies fail in group chats with error 234001
Fix
Work around Feishu group-chat voice send failures (234001 Invalid request param) by avoiding auto-TTS in groups and using DM or tagged TTS until the plugin is patched.
Telegram: bot is in a group but never responds
Fix
Fix Telegram group response issues caused by allowlist/groups config, requireMention, or Telegram privacy mode/admin permissions.
openclaw: command not found
Fix
Fix PATH issues that cause the OpenClaw CLI to be missing after install (wrong shell, npm prefix not on PATH, multiple Node installs).
Telegram + OpenClaw: Setup, Group Controls, and Common Pitfalls
Guide
Set up Telegram for OpenClaw with safe DM and group controls, privacy-mode awareness, and a verification path that proves the bot sees the right messages.
OpenClaw Installation Troubleshooting: Node/NPM, PATH, Windows (WSL2), and Docker
Guide
A layered checklist for the most common 'can't install' / 'command not found' / 'service won't start' failures. Covers Node version, global install permissions, PATH issues, WSL2 systemd, and Docker setup gotchas.