Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Cron delivery should support dynamic accountId resolution for channels with unstable session tokens (e.g. openclaw-weixin) [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#73230•Fetched 2026-04-29 06:22:01
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
sniu-gitsniu-git
Participants
clawsweeper[bot]clawsweeper[bot]sniu-gitsniu-git
Timeline (top)
commented ×1

Root Cause

Channels like openclaw-weixin generate a new accountId on every re-login or Gateway restart (because WeChat session tokens are ephemeral). This means cron jobs with a static accountId in their delivery config silently break after any update, restart, or session refresh.

Fix Action

Fix / Workaround

Each change broke all cron deliveries until manually patched.

RAW_BUFFERClick to expand / collapse

Problem

Channels like openclaw-weixin generate a new accountId on every re-login or Gateway restart (because WeChat session tokens are ephemeral). This means cron jobs with a static accountId in their delivery config silently break after any update, restart, or session refresh.

Reproduction

  1. Create a cron job with delivery.accountId = "500f19f06f5b-im-bot"
  2. Restart the Gateway or update OpenClaw
  3. WeChat plugin re-authenticates → new accountId 7345645ec687-im-bot
  4. All cron deliveries fail with: "weixin not configured: please run openclaw channels login --channel openclaw-weixin"
  5. Content is generated but never delivered. No alert unless you manually check.

Evidence

Our accountId changed 4 times in 3 days:

  • Apr 25: 500f19f06f5b-im-bot
  • Apr 26: e03a635fbb65-im-bot
  • Apr 27 11:31: 77a0c4a6a659-im-bot
  • Apr 27 14:44: 7345645ec687-im-bot (current)

Each change broke all cron deliveries until manually patched.

Proposed Solutions

Option A: Support a special placeholder like "accountId": "auto" or "accountId": "active" that resolves to the currently active account for that channel at delivery time.

Option B: When accountId is omitted or doesn't match any active account, automatically fall back to the single active account for that channel (when there's only one).

Option C: On Gateway startup, detect stale accountId references in cron jobs and either auto-update them or log a clear warning with the fix command.

Environment

  • OpenClaw 2026.4.24
  • openclaw-weixin plugin
  • WSL2 Linux

extent analysis

TL;DR

Implement a solution to dynamically resolve or update the accountId for cron jobs to prevent delivery failures due to ephemeral WeChat session tokens.

Guidance

  • Consider implementing Option A: Support a special placeholder like "accountId": "auto" or "accountId": "active" that resolves to the currently active account for that channel at delivery time.
  • Evaluate Option B: Automatically fall back to the single active account for that channel when accountId is omitted or doesn't match any active account.
  • Investigate Option C: On Gateway startup, detect stale accountId references in cron jobs and either auto-update them or log a clear warning with the fix command.
  • Verify the effectiveness of the chosen solution by monitoring cron job deliveries and accountId updates.

Example

No code snippet is provided as the issue does not contain sufficient code details.

Notes

The proposed solutions require modifications to the OpenClaw or openclaw-weixin plugin configuration or code. The chosen solution should be tested thoroughly to ensure it works as expected and does not introduce new issues.

Recommendation

Apply a workaround, such as implementing Option A or Option B, as they seem to be the most straightforward solutions to address the issue of ephemeral WeChat session tokens causing cron job delivery failures.

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…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Cron delivery should support dynamic accountId resolution for channels with unstable session tokens (e.g. openclaw-weixin) [1 comments, 2 participants]