Why did Line 2 stop at 3:05?

Why did Line 2 stop at 3:05 this morning?

Line 2 had a 42-second micro-stop at 03:05:18. The root cause was torque drift on Capper 2: the actual torque trended outside the lower control band over the preceding five samples before the line state flipped to Stopped. The capper self-corrected once the setpoint was re-applied and Line 2 resumed within spec. Evidence from the live tag history and the operator log is attached.

Has this happened before on Capper 2?

Capper 2 has logged three torque drift events in the past thirty days. All were auto-corrected and none produced a quality deviation. The pattern I can see in the data is gradual — drift accumulates over roughly two days of continuous runtime before tripping the control band. Tightening the correction cadence or adding a calibration check at the next changeover would both reduce the frequency; I can draft either one as an approval if you'd like.