Grok Bot’s routines guide says the app keeps each routine’s latest 20 run records and requires scheduled runs to be at least five minutes apart. Users can inspect successes and failures in the Routines view. The page was updated October 12, but does not identify when these limits first took effect.
At a five-minute cadence, 20 consecutive run records would represent less than two hours of activity. That is an inference from the documented limits, not a measured retention test. Someone investigating yesterday’s missed check should therefore avoid assuming it remains in the routine’s recent history. The documentation does not establish that older output files, conversation messages or backend records are deleted at the same point. Its separate files guide recommends preserving source links, timestamps, file names, an action log and anything the Bot could not verify.
Editorial take: Choose the evidence you will need later when setting up recurring work. For a frequent monitoring job, request a dated record in an appropriate, access-controlled destination, including the source checked, result and any incomplete step. Verify that this record is actually produced before depending on it. A quiet conversation can be the intended notification behavior, while a readable history still matters when a colleague asks what happened overnight. We have not tested these retention or delivery behaviors.