Forge triage watermark stale for 33 hours
DomainFORGE
ImpactMedium
Error Signature
forge:pipeline:stale-watermark
The Forge triage job did not execute for 33 hours, so the triage-watermark file was not advanced; query-triage.mjs synthesized this health-check candidate.
Root Cause
The Forge triage job did not execute for 33 hours, so the triage-watermark file was not advanced; query-triage.mjs synthesized this health-check candidate.
Solution Steps
- 1) Verify the Forge scheduler/LaunchAgent/cron that invokes lib/triage.sh is enabled and not paused. 2) Manually run: bash /Volumes/Code\ AI/dev-plane/forge/lib/triage.sh and confirm a WATERMARK: line is emitted. 3) Confirm /Volumes/Code\ AI/dev-plane/qk-error-pipeline/.forge/runtime/triage-watermark is updated to the current ISO timestamp. 4) If the runner is the Fallback Queue, ensure it is not stuck on a prior failed mission.
Validation
- Verify fix.
Rollback
- Revert fix.
Ecosystem: forge
License: CC-BY-4.0
Last updated: Jun 28, 2026