Problem
The Traces tab only shows conversation:whatsapp entries. Conversations via webchat (OpenClaw control UI) produce no traces at all.
Expected
Every channel (whatsapp, webchat, etc.) should produce traces labelled conversation:<channel>.
Likely cause
handler.ts derives the channel name from context?.channelId. Webchat events may not populate channelId in the same way WhatsApp does — it could be undefined, empty, or use a different field name — causing the trace to be silently skipped or misfiled.
Investigation
- Add debug logging to
handler.ts to dump the raw event context shape for webchat messages
- Check what field OpenClaw uses for channel identity on webchat events (
channelId vs channel vs provider etc.)
- Verify the SKIP filter isn`t dropping webchat messages (webchat heartbeat prompts look different)
Fix
Update the channel extraction in handler.ts to handle the webchat event shape, and add conversation:webchat to the test suite.
Problem
The Traces tab only shows
conversation:whatsappentries. Conversations via webchat (OpenClaw control UI) produce no traces at all.Expected
Every channel (whatsapp, webchat, etc.) should produce traces labelled
conversation:<channel>.Likely cause
handler.tsderives the channel name fromcontext?.channelId. Webchat events may not populatechannelIdin the same way WhatsApp does — it could beundefined, empty, or use a different field name — causing the trace to be silently skipped or misfiled.Investigation
handler.tsto dump the raw event context shape for webchat messageschannelIdvschannelvsprovideretc.)Fix
Update the channel extraction in
handler.tsto handle the webchat event shape, and addconversation:webchatto the test suite.