-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: Heartbeat/Cron "Current time" timestamp is stale - not refreshing between runs #44993
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.regressionBehavior that previously worked and now failsBehavior that previously worked and now failsstaleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.regressionBehavior that previously worked and now failsBehavior that previously worked and now failsstaleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
Bug type
Regression (worked before, now fails)
Summary
Heartbeat/Cron messages inject a stale "Current time" timestamp that doesn't update between runs. Shows wrong time to agent.
Steps to reproduce
Expected behavior
"Current time" should refresh to current time on each heartbeat/cron trigger
Actual behavior
Timestamp stays locked to when session started or when heartbeat was first configured. Actual time 6:22 AM but agent sees 4:22 AM (almost 2 hours stale). System prompt regenerated correctly but heartbeat message carries wrong time.
OpenClaw version
v2026.3.11
Operating system
Linux (ThinkPad P1 Gen 7)
Install method
No response
Model
minimax/MiniMax-M2.5-highspeed
Provider / routing chain
openclaw -> minimax
Config file / key location
No response
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
Related to existing timezone issues: #40586, #40029, #39579. Config: userTimezone: "America/Toronto", envelopeTimezone: "local". Workaround: restart gateway periodically to get fresh timestamps.