Skip to content

fix(cron): migrate legacy schedule cron fields on load#1516

Merged
alexey-pelykh merged 1 commit intomainfrom
cherry-pick/504c1f360-cron-migrate-legacy-schedule
Mar 16, 2026
Merged

fix(cron): migrate legacy schedule cron fields on load#1516
alexey-pelykh merged 1 commit intomainfrom
cherry-pick/504c1f360-cron-migrate-legacy-schedule

Conversation

@alexey-pelykh
Copy link
Copy Markdown

Cherry-pick of openclaw/openclaw@504c1f360.

Conflict resolution: Kept fork's normalizeStoredCronJobs() call in store.ts (fork already extracted the inline migration loop). Upstream's new jobId→id and wakeMode migrations were already present in our store-migration.ts. Deleted service.store-migration.test.ts (tests upstream's inline store.ts migration). Schedule cron→expr migration in normalize.ts, schedule.ts, and their tests applied cleanly.

Part of #681.

Backfill legacy jobs that still use schedule.cron and jobId so upgraded instances keep firing existing cron schedules instead of failing silently.

Closes openclaw#28861

(cherry picked from commit 504c1f3)
@alexey-pelykh alexey-pelykh merged commit 45c865c into main Mar 16, 2026
7 checks passed
@alexey-pelykh alexey-pelykh deleted the cherry-pick/504c1f360-cron-migrate-legacy-schedule branch March 16, 2026 08:36
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.

2 participants