Grok Bot’s approval guide, updated October 6, draws a practical distinction between active conversations and work that begins unattended. An approval requested in a chat the user is in waits for an answer. An approval arising from a routine, trigger or another Bot’s message expires after about ten minutes, and the proposed action does not run. Saving an automatic-approval rule from an expired card changes future behavior; it does not execute the expired action. The guide tells users to ask the Bot to try again.
The separate routines guide, also updated October 6, says background jobs can run while a laptop is closed, but warns that a test run performs actual work, potentially changing files or calling connected tools. It also says routines may pause after a prolonged absence if the user does not respond to a check on continued operation. These are documented operating conditions, not a newly announced failure. Together they show why a saved schedule alone cannot establish that a consequential task completed.
Editorial take: Design unattended jobs around an observable result. A morning report should say whether its sources were current and whether any step stopped for approval. For an action that needs a person, make the waiting point and recovery step explicit. Before asking for another attempt, check what already succeeded so that a partial run does not lead to a duplicate message or change.