_⚠️ Potential issue_ | _🟡 Minor_

[Neuro-Rift]

⚠️ Potential issue | 🟡 Minor

absoluteTimes entry has a past date.

The daily-summary absolute time is set to "2026-01-01T00:00:00Z", which is in the past (current date is February 2026). This job may have already triggered or might behave unexpectedly depending on the scheduler's handling of past times.

Update to a future date or convert to relative interval

-      absoluteTimes: [{ id: "daily-summary", at: "2026-01-01T00:00:00Z", mode: "isolated" }],
+      absoluteTimes: [{ id: "daily-summary", at: "2026-03-01T00:00:00Z", mode: "isolated" }],

Or consider using a recurring schedule:

-      absoluteTimes: [{ id: "daily-summary", at: "2026-01-01T00:00:00Z", mode: "isolated" }],
+      // Move daily-summary to a cron job for recurring execution

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

      absoluteTimes: [{ id: "daily-summary", at: "2026-03-01T00:00:00Z", mode: "isolated" }],

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@openclaw.json5` at line 202, The absoluteTimes entry for id "daily-summary"
in absoluteTimes uses a past timestamp ("2026-01-01T00:00:00Z"); update this to
a future ISO timestamp or replace the absoluteTimes entry with a recurring
schedule (e.g., a relative interval or cron-like schedule) so the scheduler can
run it going forward—locate the absoluteTimes array and the object with id
"daily-summary" and either set at to a future date/time or convert the object to
a recurring form (e.g., interval/cron field) consistent with the surrounding
config.

Originally posted by @coderabbitai in #27 (comment)