Severitymedium
SymptomAn unattended routine silently stops producing output after a period of owner inactivity.
CauseA deliberate safety behaviour: Grok Bot asks whether to keep routines running and pauses them if nobody responds.
DetectionAbsence of expected output. Independently described by two sources. A run can equally stop because of usage, an expired session or an unreachable source, so a missing report has several possible causes.
FixMonitor for the absence of a routine's output as a first-class alert, not just for bad output. Check routine state after any period away.