-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
Successful run completions (stopReason=stop) logged at error severity, sometimes twice per run #101678
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.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.no-staleExclude from stale automationExclude from stale automation
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.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.no-staleExclude from stale automationExclude from stale automation
Type
Fields
Priority
None yet
OpenClaw 2026.6.11 (e085fa1)
Symptom
A clean, successful run end (
stopReason=stop) is logged aterrorlevel instead ofinfo/warn. Observed logging twice for the same run (parent run id + its announce-wrapped id).Evidence
Both log lines correspond to the same underlying sub-agent run, which completed successfully (verified deliverable + git commit produced as expected).
Suggested fix
Fix log-level mapping for run completion: benign/expected stop reasons (e.g.
stop) should log atinfoorwarn; reserveerrorseverity for actual failure stop-reasons (timeouts, exceptions, aborts, etc.).Impact
Pollutes error-level log monitoring/alerting with false positives on every normal successful run, and buries genuine failures in the noise. Also appears to double-log the same run completion under two different run-id representations (raw run id and
announce:v1:...wrapped id) — worth checking whether that duplication is itself unintended.