Skip to content

fix(openclaw): restore native cron store path#161

Merged
mostlydev merged 1 commit intomasterfrom
issue-159-openclaw-cron-store
Apr 15, 2026
Merged

fix(openclaw): restore native cron store path#161
mostlydev merged 1 commit intomasterfrom
issue-159-openclaw-cron-store

Conversation

@mostlydev
Copy link
Copy Markdown
Owner

Summary

  • restore the OpenClaw native cron store mount at ~/.openclaw/cron and write jobs.json there instead of under the config directory
  • keep pod-origin OpenClaw wakes on the documented openclaw cron run <id> contract and lock the expectation with schedule-manifest tests
  • document the scheduling ownership rule in generated CLAWDAPUS.md and update the changelog / decision note to match the actual runtime contract

Root Cause

Clawdapus was generating OpenClaw cron definitions under the config directory, but current OpenClaw builds read cron definitions from ~/.openclaw/cron/jobs.json. That left openclaw cron list empty in live pods and caused openclaw cron run <id> to fail with unknown cron job id even though Clawdapus believed the jobs had been compiled.

Validation

  • go test ./...

Notes

  • This PR is the narrow cron-restoration fix needed to get Tiverton's scheduled jobs compiling into the store OpenClaw actually reads.
  • Broader managed-service freeze / health-check hardening remains follow-up work.

Closes #159
Refs #160

@mostlydev mostlydev merged commit 6418d74 into master Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix OpenClaw wake behavior for pod-origin externally scheduled invocations

1 participant