Mission Control

Automation

K

Upcoming

Clean view of what fires next across your live automations.

Recent runs healthy7 scheduled
LinkedIn Invite Scan
main
enabled
Next run
Not scheduled
Schedule
0 6 * * 1-5
Last run: Never ranAmerica/Los_Angeles
Twitter Briefing (8am)
main
enabled
Next run
Not scheduled
Schedule
0 8 * * *
Last run: Never ranAmerica/Los_Angeles
LinkedIn Jobs Morning Digest
main
paused
Next run
Not scheduled
Schedule
30 7 * * *
Last run: Never ranAmerica/Los_Angeles
Twitter Briefing (12pm)
main
enabled
Next run
Not scheduled
Schedule
0 12 * * *
Last run: Never ranAmerica/Los_Angeles
Twitter Briefing (4pm)
main
enabled
Next run
Not scheduled
Schedule
0 16 * * *
Last run: Never ranAmerica/Los_Angeles
Twitter Briefing Manual Test (today 6:05pm)
main
paused
Next run
Not scheduled
Schedule
No cron expression
Last run: Never ranAmerica/Los_Angeles
Lantronix Radar (9am)
main
enabled
Next run
Not scheduled
Schedule
0 9 * * *
Last run: Never ranAmerica/Los_Angeles
openclaw-release-monitor
main
enabled
Next run
Not scheduled
Schedule
0 10 * * 1,3,5
Last run: Never ranAmerica/Los_Angeles
Workspace Auto-Commit
david
paused
Next run
Not scheduled
Schedule
*/30 * * * *
Last run: Never ranAmerica/Los_Angeles
Workspace Auto-Commit
unknown
enabled
Next run
Not scheduled
Schedule
*/30 * * * *
Last run: Never ranAmerica/Los_Angeles
LinkedIn Invite Scan retry after browser restart
main
paused
Next run
Not scheduled
Schedule
No cron expression
Last run: Never ranAmerica/Los_Angeles
LinkedIn Invite Scan retry after gateway restart
main
paused
Next run
Not scheduled
Schedule
No cron expression
Last run: Never ranAmerica/Los_Angeles

Needs Attention

Failed automation runs from the last 24 hours, with quick investigation summaries and next fixes.

1 failed run
openclaw-release-monitor
Execution timeouthigh confidenceJun 1, 10:00 AM · 16 hours ago
cron: job execution timed out
Likely cause
The job ran until OpenClaw killed it for taking too long. The run hit 5m 1s, which lines up with a hard timeout.
Evidence
  • cron: job execution timed out
  • Observed runtime: 5m 1s
  • main • 0 10 * * 1,3,5 • 300s timeout
Proposed fixes
  1. Trim the job scope so it does less work per run, for example fewer search results or a shorter summarization window.
  2. Increase the cron timeoutSeconds for this job if the longer runtime is expected and acceptable.
  3. Check whether the job is blocking on browser or network work, then move that step into a faster path or cache more aggressively.
Seen 7 similar failures in the stored history for this job.

Recent Activity

Compact run history from the live logs.

1
Workspace Auto-Commit
ok5 minutes agoJun 2, 2:00 AM
Duration: 0sDelivery: not-requestedNext: in 25 minutes
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
2
Workspace Auto-Commit
ok35 minutes agoJun 2, 1:30 AM
Duration: 0sDelivery: not-requestedNext: 5 minutes ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
3
Workspace Auto-Commit
ok1 hour agoJun 2, 1:00 AM
Duration: 0sDelivery: not-requestedNext: 35 minutes ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
4
Workspace Auto-Commit
ok2 hours agoJun 2, 12:30 AM
Duration: 0sDelivery: not-requestedNext: 1 hour ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
5
Workspace Auto-Commit
ok2 hours agoJun 2, 12:00 AM
Duration: 0sDelivery: not-requestedNext: 2 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
6
Workspace Auto-Commit
ok3 hours agoJun 1, 11:30 PM
Duration: 0sDelivery: not-requestedNext: 2 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
7
Workspace Auto-Commit
ok3 hours agoJun 1, 11:00 PM
Duration: 0sDelivery: not-requestedNext: 3 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
8
Workspace Auto-Commit
ok4 hours agoJun 1, 10:30 PM
Duration: 0sDelivery: not-requestedNext: 3 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
9
Workspace Auto-Commit
ok4 hours agoJun 1, 10:00 PM
Duration: 0sDelivery: not-requestedNext: 4 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
10
Workspace Auto-Commit
ok5 hours agoJun 1, 9:30 PM
Duration: 0sDelivery: not-requestedNext: 4 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
11
Workspace Auto-Commit
ok5 hours agoJun 1, 9:00 PM
Duration: 0sDelivery: not-requestedNext: 5 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
12
Workspace Auto-Commit
ok6 hours agoJun 1, 8:30 PM
Duration: 0sDelivery: not-requestedNext: 5 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
13
Workspace Auto-Commit
ok6 hours agoJun 1, 8:00 PM
Duration: 0sDelivery: not-requestedNext: 6 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
14
Workspace Auto-Commit
ok7 hours agoJun 1, 7:30 PM
Duration: 0sDelivery: not-requestedNext: 6 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
15
Workspace Auto-Commit
ok7 hours agoJun 1, 7:00 PM
Duration: 0sDelivery: not-requestedNext: 7 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto
16
Workspace Auto-Commit
ok8 hours agoJun 1, 6:30 PM
Duration: 0sDelivery: not-requestedNext: 7 hours ago
bash /Users/vinny/.openclaw/workspace/scripts/workspace-commit.sh --auto