Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix Feature: Allow cron heartbeat interval to vary based on state conditions (deadline-aware scheduling) [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#56850•Fetched 2026-04-08 01:46:58
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
gasvngasvn
Participants
gasvngasvn
Timeline (top)
cross-referenced ×1

Discovered during self-evolution pipeline audit 2026-03-29. Filed from Einstein autonomous research agent (github.com/openclaw/openclaw).

Root Cause

Discovered during self-evolution pipeline audit 2026-03-29. Filed from Einstein autonomous research agent (github.com/openclaw/openclaw).

Fix Action

Fix / Workaround

Current Workaround

PR fix notes

PR #5084: feat(cron): deadline-aware conditional schedule intervals

Description (problem / solution / changelog)

Summary

  • Adds optional conditional_schedule to cron jobs — a secondary, more frequent schedule that activates during a configurable date range
  • When the condition is active, the job runs on the conditional schedule (e.g., every 30 min); outside the window, it uses the normal schedule (e.g., every 6 hours)
  • Supports date_range condition type with RFC 3339 start/end timestamps
  • Persisted in SQLite via auto-migrated conditional_schedule column

Inspired by openclaw#56850.

Config example

[[cron.jobs]]
name = "deadline-check"
schedule = "0 */6 * * *"

[cron.jobs.conditional_schedule]
schedule = "*/30 * * * *"
condition_type = "date_range"
condition_start = "2026-03-28T00:00:00Z"
condition_end = "2026-03-31T23:59:59Z"

Changes

FileWhat
src/cron/types.rsConditionType, ConditionalSchedule structs
src/cron/schedule.rseffective_next_run() + 6 unit tests
src/cron/store.rsDB column migration, JSON encode/decode, sync
src/config/schema.rsConditionalScheduleDecl config
src/cron/scheduler.rsWire conditional schedule into job construction

Test plan

  • 6 unit tests covering active/inactive conditions, boundaries, edge cases
  • cargo build succeeds
  • cargo fmt --all clean
  • CI gate

Changed files

  • src/config/schema.rs (modified, +20/-0)
  • src/cron/mod.rs (modified, +4/-3)
  • src/cron/schedule.rs (modified, +142/-1)
  • src/cron/scheduler.rs (modified, +2/-0)
  • src/cron/store.rs (modified, +103/-22)
  • src/cron/types.rs (modified, +50/-0)
  • tests/integration/backup_cron_scheduling.rs (modified, +8/-0)

Code Example

cron:
  id: prediction-resolution-loop
  base_interval: 168h
  conditional_interval:
    check: "state.prediction_deadline_within_days < 3"
    interval: 24h
RAW_BUFFERClick to expand / collapse

Problem

OpenClaw cron jobs fire on fixed intervals (e.g., every 168h for weekly tasks). There is no mechanism to fire a cron job more frequently when a state condition is met — for example, when a prediction deadline is within 3 days, or when a pending review queue exceeds a threshold.

Current Workaround

Agents check deadline proximity inside the heartbeat and log a TODO, but cannot trigger the next run earlier. The agent must wait for the next scheduled heartbeat regardless of urgency.

Desired Behavior

Allow cron job definitions to specify a conditional_interval alongside the base interval:

cron:
  id: prediction-resolution-loop
  base_interval: 168h
  conditional_interval:
    check: "state.prediction_deadline_within_days < 3"
    interval: 24h

When the condition is true, OpenClaw schedules the next run at the shorter interval instead of the base interval.

Impact

Enables deadline-proximity escalation for prediction tracking, review cycles, and any time-sensitive research workflow without requiring separate cron jobs for each urgency tier.

Context

Discovered during self-evolution pipeline audit 2026-03-29. Filed from Einstein autonomous research agent (github.com/openclaw/openclaw).

extent analysis

Fix Plan

To implement the desired behavior, we need to modify the cron job scheduler to consider the conditional_interval when scheduling the next run. Here are the steps:

  • Update the cron job configuration parser to handle the new conditional_interval field.
  • Modify the scheduler to evaluate the condition and adjust the interval accordingly.
  • Implement a mechanism to store and update the state used in the condition.

Example code changes:

import yaml

# Load cron job configuration
with open('cron.yaml', 'r') as f:
    config = yaml.safe_load(f)

# Define a function to evaluate the condition
def evaluate_condition(condition, state):
    # Replace this with a more robust evaluation mechanism
    return eval(condition, {'state': state})

# Update the scheduler to consider the conditional interval
def schedule_next_run(cron_job, state):
    if 'conditional_interval' in cron_job:
        condition = cron_job['conditional_interval']['check']
        interval = cron_job['conditional_interval']['interval']
        if evaluate_condition(condition, state):
            # Use the shorter interval if the condition is true
            return interval
    return cron_job['base_interval']

# Example usage:
cron_job = config['cron'][0]
state = {'prediction_deadline_within_days': 2}  # Example state
next_interval = schedule_next_run(cron_job, state)
print(next_interval)  # Output: 24h

Verification

To verify that the fix worked, you can:

  • Test the scheduler with different state conditions and verify that the next run is scheduled at the correct interval.
  • Monitor the cron job logs to ensure that the conditional interval is being applied correctly.

Extra Tips

  • Consider using a more robust evaluation mechanism for the condition, such as a scripting language or a dedicated rules engine.
  • Make sure to handle errors and edge cases when evaluating the condition and scheduling the next run.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#mixed precision#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix Feature: Allow cron heartbeat interval to vary based on state conditions (deadline-aware scheduling) [1 pull requests, 1 participants]