Grok Bot’s October 23 changelog raises the combined routine ceiling from 100 to 300 runs an hour and lists a limit of 200 for an individual routine. That is additional headroom, not a promise that scheduled jobs can run every few seconds. The current Skills and routines guide still says schedules must be at least five minutes apart. This analysis compares the two documented limits; we have not measured throughput, latency or concurrent execution.
The distinction matters because the guide describes both scheduled routines and work triggered by supported events, such as Slack messages or GitHub notifications. It recommends narrow matching rules rather than a listener for every message. A larger hourly allowance could accommodate more relevant events without changing a scheduled check’s cadence. Neither source establishes how excess triggers are queued, retried or discarded, so a workflow should not assume a delivery guarantee from the ceiling alone.
Editorial take: Plan the trigger before spending the extra capacity. For a support workflow, a specific ticket link and escalation phrase are more useful filters than every channel message. State which events warrant action, which only need a summary and what should happen when inputs are missing. Then test a bounded example and inspect the actual result before broadening the rule. The aim is more useful work, not simply more runs.