Mission Control

Automation

K

Upcoming

Clean view of what fires next across your live automations.

6 recent errors14 scheduled
Browser Relay Check (5:45am weekdays)
main
enabled
Next run
in 2 hours
Schedule
45 5 * * 1-5
Last run: 22 hours agoAmerica/Los_Angeles
LinkedIn Invite Scan
main
enabled
Next run
in 2 hours
Schedule
0 6 * * 1-5
Last run: 22 hours agoAmerica/Los_Angeles
LinkedIn Jobs Morning Digest
main
enabled
Next run
in 4 hours
Schedule
30 7 * * *
Last run: 20 hours agoAmerica/Los_Angeles
Browser Relay Check (7:45am)
main
enabled
Next run
in 4 hours
Schedule
45 7 * * *
Last run: 20 hours agoAmerica/Los_Angeles
Twitter Briefing (8am)
main
enabled
Next run
in 4 hours
Schedule
0 8 * * *
Last run: 20 hours agoAmerica/Los_Angeles
Lantronix Radar (9am)
main
enabled
Next run
in 5 hours
Schedule
0 9 * * *
Last run: 16 hours agoAmerica/Los_Angeles
Browser Relay Check (11:45am)
main
enabled
Next run
in 8 hours
Schedule
45 11 * * *
Last run: 16 hours agoAmerica/Los_Angeles
Twitter Briefing (12pm)
main
enabled
Next run
in 8 hours
Schedule
0 12 * * *
Last run: 16 hours agoAmerica/Los_Angeles
Browser Relay Check (3:45pm)
main
enabled
Next run
in 12 hours
Schedule
45 15 * * *
Last run: 12 hours agoAmerica/Los_Angeles
Twitter Briefing (4pm)
main
enabled
Next run
in 12 hours
Schedule
0 16 * * *
Last run: 12 hours agoAmerica/Los_Angeles
Browser Relay Check (9pm EOD)
main
enabled
Next run
in 17 hours
Schedule
0 21 * * *
Last run: 7 hours agoAmerica/Los_Angeles
openclaw-release-monitor
main
enabled
Next run
in 30 hours
Schedule
0 10 * * 1,3,5
Last run: 16 hours agoAmerica/Los_Angeles
openclaw-upgrade-readiness-check
main
enabled
Next run
in 5 days
Schedule
No cron expression
Last run: Never ranAmerica/Los_Angeles
AgentArmor Homebrew Check
main
enabled
Next run
in 11 days
Schedule
No cron expression
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: 18 days agoAmerica/Los_Angeles

Needs Attention

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

5 failed runs
Browser Relay Check (9pm EOD)
Execution timeouthigh confidenceApr 1, 9:00 PM · 7 hours ago
cron: job execution timed out
Likely cause
The job ran until OpenClaw killed it for taking too long. The run hit 1m 0s, which lines up with a hard timeout.
Evidence
  • cron: job execution timed out
  • Observed runtime: 1m 0s
  • main • 0 21 * * * • 60s 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.
Twitter Briefing (12pm)
Execution timeouthigh confidenceApr 1, 12:00 PM · 16 hours ago
cron: job execution timed out
Likely cause
The job ran until OpenClaw killed it for taking too long. The run hit 10m 0s, which lines up with a hard timeout.
Evidence
  • cron: job execution timed out
  • Observed runtime: 10m 0s
  • main • 0 12 * * * • 600s 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 2 similar failures in the stored history for this job.
openclaw-release-monitor
Delivery failedhigh confidenceApr 1, 11:36 AM · 16 hours ago
⚠️ ✉️ Message failed
Likely cause
The agent seems to have produced output, but the final delivery step failed or was rejected.
Evidence
  • ⚠️ ✉️ Message failed
  • Run summary exists, so content generation likely completed.
Proposed fixes
  1. Check the delivery target and provider credentials for this job, then send a manual test message.
  2. If the destination changed, update the stored channel or chat ID in the cron config.
  3. Keep the output generation the same, but make delivery failures louder by logging the exact provider response.
Seen 3 similar failures in the stored history for this job.
openclaw-release-monitor
Delivery failedhigh confidenceApr 1, 10:00 AM · 18 hours ago
⚠️ ✉️ Message failed
Likely cause
The agent seems to have produced output, but the final delivery step failed or was rejected.
Evidence
  • ⚠️ ✉️ Message failed
  • Run summary exists, so content generation likely completed.
Proposed fixes
  1. Check the delivery target and provider credentials for this job, then send a manual test message.
  2. If the destination changed, update the stored channel or chat ID in the cron config.
  3. Keep the output generation the same, but make delivery failures louder by logging the exact provider response.
Seen 3 similar failures in the stored history for this job.
Lantronix Radar (9am)
Execution timeouthigh confidenceApr 1, 9:00 AM · 19 hours ago
cron: job execution timed out
Likely cause
The job ran until OpenClaw killed it for taking too long. The run hit 5m 0s, which lines up with a hard timeout.
Evidence
  • cron: job execution timed out
  • Observed runtime: 5m 0s
  • main • 0 9 * * * • 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.

Recent Activity

Compact run history from the live logs.

1
Browser Relay Check (9pm EOD)
error7 hours agoApr 1, 9:00 PM
Duration: 1m 0sDelivery: not-requestedNext: in 17 hours
cron: job execution timed out
2
Twitter Briefing (4pm)
ok12 hours agoApr 1, 4:00 PM
Duration: 1m 50sDelivery: not-deliveredNext: in 12 hoursopenai-codex • gpt-5.4
Posted 5 stories to #news-feed. No Recommendations sent.
3
Browser Relay Check (3:45pm)
ok12 hours agoApr 1, 3:45 PM
Duration: 56sDelivery: not-deliveredNext: in 12 hoursopenai-codex • gpt-5.4
Browser relay check failed, profile `chrome` was not reachable. I sent Pete the Discord DM alert.
4
Twitter Briefing (12pm)
error16 hours agoApr 1, 12:00 PM
Duration: 10m 0sDelivery: not-requestedNext: in 8 hours
cron: job execution timed out
5
Browser Relay Check (11:45am)
ok16 hours agoApr 1, 11:45 AM
Duration: 10sDelivery: not-deliveredNext: in 8 hoursanthropic • claude-sonnet-4-6
Relay is connected and ready. `chrome-relay` is up on port 18792, CDP is responsive. No action needed.
6
openclaw-release-monitor
error16 hours agoApr 1, 11:36 AM
Duration: 1m 50sDelivery: not-deliveredNext: in 30 hoursanthropic • claude-sonnet-4-6
⚠️ ✉️ Message failed
Memory already has the last reported release updated (looks like it was written during this run correctly). The job is done. **Summary:** Found two new stable …
7
Lantronix Radar (9am)
ok16 hours agoApr 1, 11:33 AM
Duration: 3m 37sDelivery: not-deliveredNext: in 5 hoursanthropic • claude-sonnet-4-6
**Internal status summary:** Run complete — April 1, 2026 (9am cron, fired at 11:33am PT). - **Stories posted to #uas-news:** 4 (Defense market sizing, Skyport…
8
openclaw-release-monitor
error18 hours agoApr 1, 10:00 AM
Duration: 2m 24sDelivery: not-deliveredNext: in 30 hoursanthropic • claude-sonnet-4-6
⚠️ ✉️ Message failed
Done. Found two new stable releases (v2026.3.31 and v2026.4.1) with no prior report in memory, so I posted an analysis to #openclaw-releases and recorded v2026…
9
Lantronix Radar (9am)
error19 hours agoApr 1, 9:00 AM
Duration: 5m 0sDelivery: not-requestedNext: in 5 hours
cron: job execution timed out
10
Twitter Briefing (8am)
ok20 hours agoApr 1, 8:00 AM
Duration: 1m 18sDelivery: not-deliveredNext: in 4 hoursanthropic • claude-sonnet-4-6
**Internal status:** Run failed. Chrome not running at cron trigger time (8:00 AM PT). Browser relay (all profiles) unavailable. No stories scraped, no Discord…
11
Browser Relay Check (7:45am)
ok20 hours agoApr 1, 7:45 AM
Duration: 14sDelivery: not-deliveredNext: in 4 hoursanthropic • claude-sonnet-4-6
Relay is connected and ready. No action needed. **Status:** Chrome relay is up (`cdpReady: true`, port 18792). Twitter Briefing at 8am is good to go.
12
LinkedIn Jobs Morning Digest
ok20 hours agoApr 1, 7:30 AM
Duration: 1m 51sDelivery: not-deliveredNext: in 4 hoursanthropic • claude-sonnet-4-6
**Status:** Digest complete. 8 new roles posted as individual cards to #job-alerts (132 dupes skipped, 15 blacklisted). Top pick is the AI Consulting Leader at…
13
LinkedIn Invite Scan
ok22 hours agoApr 1, 6:00 AM
Duration: 2m 5sDelivery: deliveredNext: in 2 hoursanthropic • claude-sonnet-4-6
Browser relay isn't active (no badge tab). Sent Pete a message in #vinny asking him to activate the relay and re-trigger the scan.
14
Browser Relay Check (5:45am weekdays)
ok22 hours agoApr 1, 5:45 AM
Duration: 10sDelivery: not-deliveredNext: in 2 hoursanthropic • claude-sonnet-4-6
Browser relay is connected and ready. No action needed. **Status:** ✅ Chrome relay is up (port 18792, CDP ready) — LinkedIn Invite Scan at 6:00am is good to go.
15
Browser Relay Check (9pm EOD)
error31 hours agoMar 31, 9:00 PM
Duration: 27sDelivery: not-deliveredNext: 7 hours agoanthropic • claude-sonnet-4-6
⚠️ 🌐 Browser failed
⚠️ 🌐 Browser failed
16
Twitter Briefing (4pm)
ok36 hours agoMar 31, 4:00 PM
Duration: 2m 53sDelivery: not-deliveredNext: 12 hours agoanthropic • claude-sonnet-4-6
**Internal status:** 4pm briefing complete. Browser unavailable (Chrome not running), fell back to web search. 5 stories posted to #news-feed: GPT-5.4 release,…