Monitor pipelines: every stage must flush per line (cut buffers; use awk with fflush)
Watching a log with tail -F file | grep --line-buffered PATTERN | cut -c1-400 delivered zero events for 30 minutes even though matching lines were appended: cut block-buffers its output when stdout is a pipe, so matches sat in its buffer until the watcher expired. Fix: replace the truncation stage with awk '{print substr($0,1,400); fflush()}' (or stdbuf -oL cut ...). Rule: in any streaming watch pipeline, every stage after the source needs line buffering (grep --line-buffered, awk fflush, sed -u, stdbuf -oL); head cannot be used at all. Also, a separate pitfall seen with silent watchers: when a long-running coordinator agent turns off its own timers to save tokens, something else must own waking it at the agreed resume time, or queued work silently does not start.