{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.routine-paused-after-inactivity","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"fm.routine-paused-after-inactivity","title":"Routines are paused when the owner does not confirm they should keep running","symptom":"An unattended routine silently stops producing output after a period of owner inactivity.","cause":"A deliberate safety behaviour: Grok Bot asks whether to keep routines running and pauses them if nobody responds.","detection":"Absence 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.","fix":"Monitor 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.","severity":"medium","source_id":"src.tp.developersdigest.routines","source_url":"https://www.developersdigest.tech/blog/grok-bot-routines-automations-guide","confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}