Scheduled jobs
6
Live cron inventory from OpenClaw runtime files, not a UI-only planner.
Healthy schedules
6
builder-mission-control-loop · Every 15m
Heartbeat
On
Heartbeat prompt file exists. Runtime delivery still depends on live gateway health. · updated 4h ago
Upcoming automation
builder-mission-control-loophealthy
Every 15m · 4/8/2026, 6:20:36 AM (in 2m)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
healthfit-watchhealthy
Every 60m · 4/8/2026, 7:15:09 AM (in 56m)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
afternoon-briefhealthy
30 16 * * 1-5 (America/Los_Angeles) · 4/8/2026, 7:30:00 AM (in 1h)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
morning-briefhealthy
30 7 * * 1-5 (America/Los_Angeles) · 4/8/2026, 10:30:00 PM (in 16h)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
friday-digesthealthy
0 15 * * 5 (America/Vancouver) · 4/11/2026, 6:00:00 AM (in 3d)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
sunday-prephealthy
30 19 * * 0 (America/Vancouver) · 4/13/2026, 10:30:00 AM (in 5d)
Last status: ok · Source: /data/.openclaw/cron/jobs.json
Recent automation outcomes
healthfit-watch finishedcron
1. Change detected
Fresh 2026-04-06 recovery data shows a meaningful recovery dip.
2. Key data
No new workout.
Recovery markers: HRV… · 4/8/2026, 6:16:14 AM
builder-mission-control-loop finishedcron
I hit a real blocker: Next’s build cache has a root-owned file, so normal verification can’t clean or rewrite `.next/diagnostics/build-diag… · 4/8/2026, 6:08:56 AM
builder-mission-control-loop finishedcron
Added the first real `/office` slice to Mission Control.
- Changed: new `/office` route built from live adapter data, showing an operating… · 4/8/2026, 5:53:53 AM
healthfit-watch finishedcron
1. Change detected
Recovery metrics rolled to 2026-04-06 and show a mild recovery flag.
2. Key data
No new workout.
Recovery: HRV 42… · 4/8/2026, 5:15:46 AM
afternoon-brief finishedcron
Afternoon brief
What moved today
- Build-side work moved in Notion today:
- Mission Control Dashboard logged as Planned, with the archit… · 4/8/2026, 1:04:46 AM
Cron vs heartbeat
Cronruntime
Scheduled jobs and run history come from OpenClaw cron runtime state.
Heartbeatwarning
Heartbeat is shown separately as an agent loop signal, not mixed into cron inventory.
Current signalerror
Gateway check failed: [1m[91mConfig invalid[39m[22m
Schedule sources
Gateway adapterDegraded
openclaw gateway status --json
HeartbeatConfigured
workspace-builder/HEARTBEAT.md presence
Cron runtimeDegraded
[1m[91mConfig invalid[39m[22m
Cron inventory6 jobs
/data/.openclaw/cron/jobs.json