-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
Bug Report
Plugin version: 1.0.4
OpenClaw version: 2026.2.9
Problem
Automatic message logging (auto-add on each user message) returns HTTP 200 but with "status": "failed" in the response body.
Example Request
{
"content": "[role: user]\n[Telegram Macher id:-1003541168386 topic:1 +1m Sun 2026-02-22 04:09 GMT+1] Benedikt B...",
"containerTag": "openclaw_Mac_mini_von_Benedikt_local",
"metadata": {
"source": "openclaw",
"timestamp": "2026-02-22T03:10:14.873Z"
},
"customId": "session_agent_main_telegram_group_1003541168386_topic_1"
}Response (HTTP 200)
{
"response": {
"id": "VFscjj9mi9HL5CfnKemfqv",
"status": "failed"
},
"type": "add"
}Notes
- Explicit
supermemory_storetool calls work fine and return success. - Only the automatic per-message logging fails consistently.
- Visible in the Supermemory console dashboard.
- Possibly related to content length or format of raw Telegram messages with metadata.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels