openclaw - 💡(How to fix) Fix [Bug]: hasExplicitHeartbeatAgents ignores global heartbeat defaults when any agent has explicit config [3 comments, 2 participants]

Bug Description

When any agent in agents.list has an explicit heartbeat config, the global agents.defaults.heartbeat setting is completely ignored for all other agents that don't have their own heartbeat config.

A single agent with heartbeat: { "every": "0m" } inadvertently disables heartbeat for ALL other agents relying on the global default.

Root Cause

In heartbeat-summary.ts, isHeartbeatEnabledForAgent:

function isHeartbeatEnabledForAgent(cfg, agentId) {
  if (hasExplicitHeartbeatAgents(cfg)) {
    return list.some(entry => Boolean(entry?.heartbeat) && entry.id === agentId);
  }
  if (cfg.agents?.defaults?.heartbeat) return true;
}

hasExplicitHeartbeatAgents checks if any agent has a heartbeat config. If so, only agents with explicit heartbeat are enabled — the global default is never consulted.

Reproduction

{
  "agents": {
    "defaults": {
      "heartbeat": { "every": "600m" }
    },
    "list": [
      { "id": "main" },
      { "id": "sexmaid", "heartbeat": { "every": "0m" } }
    ]
  }
}

Expected: main uses global default 600m heartbeat. Actual: main heartbeat is disabled — hasExplicitHeartbeatAgents returns true (due to sexmaid), and main has no explicit heartbeat config.

Impact

• Cron jobs targeting session: main silently skipped with "error": "disabled"
• System event enqueued but never processed (runHeartbeatOnce returns skipped)
• No user visibility into why main session cron jobs fail