openclaw - 💡(How to fix) Fix Fix session reset reason param rejected by OpenClaw RPC schema [1 comments, 2 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#48811Fetched 2026-04-08 00:52:15
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1locked ×1
RAW_BUFFERClick to expand / collapse

OpenClaw sessions.reset RPC validates the reason parameter against a strict schema that only accepts "reset" as a constant. Our code was sending "poisoned-session" which fails with: invalid sessions.reset params: at /reason: must be equal to constant; at /reason: must match a schema in anyOf

Fix: change reason from "poisoned-session" to "reset" in both the WhatsApp plugin and admin route.

extent analysis

Fix Plan

To resolve the issue, update the reason parameter in the sessions.reset RPC call to match the expected schema.

  • In the WhatsApp plugin, replace "poisoned-session" with "reset":
# Before
sessions.reset(reason="poisoned-session")

# After
sessions.reset(reason="reset")
  • In the admin route, make the same change:
# Before
sessions.reset(reason="poisoned-session")

# After
sessions.reset(reason="reset")

Verification

After applying the fix, verify that the sessions.reset RPC call no longer returns an error. You can test this by calling the RPC method with the updated reason parameter and checking the response for success.

Extra Tips

  • Ensure that all instances of the sessions.reset call are updated to use the correct reason parameter to avoid similar errors in the future.
  • Consider adding a check or validation in your code to ensure that the reason parameter is set to the expected value before making the RPC call.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING