openclaw - 💡(How to fix) Fix [Bug]: 4.1: Unable to resolve bundled plugin error on image-generation-core/runtime-api.js and telegram module in cron jobs [1 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#59901Fetched 2026-04-08 02:39:02
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

After a clean install of [email protected] (via npm uninstall -g openclaw && npm install -g openclaw@latest), several cron jobs are failing with module resolution errors. This appears to be a bug in how bundled plugins are resolved in isolated cron sessions.

Root Cause

After a clean install of [email protected] (via npm uninstall -g openclaw && npm install -g openclaw@latest), several cron jobs are failing with module resolution errors. This appears to be a bug in how bundled plugins are resolved in isolated cron sessions.

Fix Action

Fix / Workaround

This is preventing several core cron jobs from running. Disabling the affected crons is the only current workaround. Let me know if you need more diagnostic info.

Code Example

Isolated cron session crashes at boot with:
"Unable to resolve bundled plugin public surface image-generation-core/runtime-api.js"
or
"Cannot find module '/usr/local/lib/node_modules/openclaw/dist/telegram-B2Tb4iqk.js'"

Job exits immediately with consecutiveErrors incremented. No agent turn executes.

---

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Description

After a clean install of [email protected] (via npm uninstall -g openclaw && npm install -g openclaw@latest), several cron jobs are failing with module resolution errors. This appears to be a bug in how bundled plugins are resolved in isolated cron sessions.

Errors

Two distinct errors have been observed:

  1. Alpha Daily Intel cron: Unable to resolve bundled plugin public surface image-generation-core/runtime-api.js

  2. Daily Executive Comms Coaching cron: Cannot find module '/usr/local/lib/node_modules/openclaw/dist/telegram-B2Tb4iqk.js' imported from /usr/local/lib/node_modules/openclaw/dist/deps-VXXmQP1k.js

Investigation

The image-generation-core/runtime-api.js file does exist on disk at: /usr/local/lib/node_modules/openclaw/dist/extensions/image-generation-core/runtime-api.js

grep shows that it is referenced correctly in several .d.ts type definition files, but the runtime resolution is failing in the context of an isolated cron session. This suggests the module manifest or bundler output in 4.1 has a path resolution issue for certain plugins when a cron job boots up.

The telegram*.js file also exists, pointing to the same category of path resolution bug in isolated sessions.

Environment

  • OpenClaw version: 2026.4.1 (da64a97)
  • Install method: npm latest tag (clean install)
  • OS: macOS 24.6.0 (x64)
  • Node: v22.22.0
  • Session type: Isolated cron (sessionTarget: "isolated")

This is preventing several core cron jobs from running. Disabling the affected crons is the only current workaround. Let me know if you need more diagnostic info.

Steps to reproduce

  1. Run: npm uninstall -g openclaw && npm install -g openclaw@latest
  2. Confirm version: openclaw --version → 2026.4.1
  3. Start gateway: openclaw gateway start
  4. Create or wait for any cron job with sessionTarget: "isolated" to fire
  5. Check cron status: openclaw cron list → observe lastError on affected jobs

Expected behavior

Isolated cron sessions should boot successfully and resolve all bundled plugin modules. Jobs like Alpha Daily Intel and Coaching prompts should execute without module resolution errors.

Actual behavior

Isolated cron session crashes at boot with:
"Unable to resolve bundled plugin public surface image-generation-core/runtime-api.js"
or
"Cannot find module '/usr/local/lib/node_modules/openclaw/dist/telegram-B2Tb4iqk.js'"

Job exits immediately with consecutiveErrors incremented. No agent turn executes.

OpenClaw version

2026.4.1

Operating system

macOS 15.7.5

Install method

npm

Model

anthropic claude sonnet 4.6

Provider / routing chain

openclaw → anthropic/claude-sonnet-4-6

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix involves adjusting the module resolution or bundler configuration to correctly resolve bundled plugins in isolated cron sessions.

Guidance

  • Verify that the image-generation-core/runtime-api.js and telegram-B2Tb4iqk.js files exist in the expected locations and are correctly referenced in the project's type definitions and module manifests.
  • Investigate the differences in module resolution between the main application and isolated cron sessions to identify potential configuration discrepancies.
  • Consider temporarily modifying the sessionTarget to a non-isolated mode to see if the issue persists, which could help isolate the problem to the session type.
  • Review the OpenClaw documentation and version history to see if there are any known issues or changes related to module resolution in isolated sessions.

Example

No specific code example is provided due to the lack of explicit code references in the issue description.

Notes

The issue seems to be related to the specific version of OpenClaw (2026.4.1) and the isolated cron session configuration. Further investigation into the module resolution and bundling process is needed to determine the root cause.

Recommendation

Apply a workaround by adjusting the sessionTarget to a non-isolated mode until a permanent fix is available, as this may allow the cron jobs to run successfully.

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…

FAQ

Expected behavior

Isolated cron sessions should boot successfully and resolve all bundled plugin modules. Jobs like Alpha Daily Intel and Coaching prompts should execute without module resolution errors.

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 [Bug]: 4.1: Unable to resolve bundled plugin error on image-generation-core/runtime-api.js and telegram module in cron jobs [1 participants]