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, checking your installed version, and using the stable update guide if your build lowercases base64 IDs.
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) Check your version and use the stable update guide if needed
If your installed version lowercases group IDs, confirm the current stable path in the update guide, update or pin as appropriate for your deployment, and restart the gateway. Do not assume a specific release fixed this unless the release evidence says so.
Verify
- A test send to
signal:group:<groupId>succeeds. - The group receives the message.