openclaw - 💡(How to fix) Fix Feishu delivery not working for cron jobs: runtime not initialized [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#48889Fetched 2026-04-08 00:51:27
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×1cross-referenced ×1subscribed ×1

Error Message

`"error": "Error: Feishu runtime not initialized"` and `deliveryStatus: "unknown"`

Code Example

openclaw cron edit <id> --announce --channel feishu --to "chat:oc_xxx"
RAW_BUFFERClick to expand / collapse

Bug

Cron job delivery to Feishu channel fails with `Feishu runtime not initialized` when using `--announce --channel feishu --to chat:oc_xxx`.

Steps to reproduce

  1. Configure Feishu channel with WebSocket mode (verified ON | OK)
  2. Create a cron job with delivery targeting Feishu:
    openclaw cron edit <id> --announce --channel feishu --to "chat:oc_xxx"
  3. Run the cron job

Expected

Agent reply should be delivered to the Feishu chat.

Actual

`"error": "Error: Feishu runtime not initialized"` and `deliveryStatus: "unknown"`

Notes

  • Feishu WebSocket is connected and working (DM messages work fine)
  • Same cron job delivers successfully to Discord
  • The Feishu runtime store (`createPluginRuntimeStore`) is only initialized when the WS client starts, but cron isolated sessions cannot access it
  • OpenClaw version: 2026.3.13
  • Channel mode: websocket
  • Config: single account, dmPolicy: pairing

extent analysis

Fix Plan

To resolve the "Feishu runtime not initialized" error, we need to ensure the Feishu runtime store is accessible to cron isolated sessions.

Here are the steps:

  • Modify the createPluginRuntimeStore function to initialize the Feishu runtime store for cron jobs.
  • Update the cron job delivery logic to use the initialized Feishu runtime store.

Code Changes

// Initialize Feishu runtime store for cron jobs
function createPluginRuntimeStoreForCron() {
  // Initialize Feishu runtime store
  const feishuRuntimeStore = initializeFeishuRuntimeStore();
  // Store the Feishu runtime store in a shared location accessible to cron jobs
  cronJobContext.feishuRuntimeStore = feishuRuntimeStore;
}

// Update cron job delivery logic to use the initialized Feishu runtime store
function deliverToFeishu(cronJob) {
  // Get the Feishu runtime store from the shared location
  const feishuRuntimeStore = cronJobContext.feishuRuntimeStore;
  // Use the Feishu runtime store to deliver the message
  deliverMessageToFeishu(cronJob, feishuRuntimeStore);
}

Verification

To verify the fix, run the cron job again and check the delivery status. The message should be delivered to the Feishu chat successfully.

Extra Tips

  • Ensure the createPluginRuntimeStoreForCron function is called before running the cron job.
  • Verify that the Feishu runtime store is properly initialized and stored in a shared location accessible to cron jobs.
  • Test the fix with different cron jobs and Feishu channels to ensure the issue is fully resolved.

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