The correct scheduling mode is Continuous . Continuous scheduling is designed for cases where the engineer wants the scheduled search to preserve coverage of every intended time interval, even if a particular execution cannot start exactly at its configured time.
With continuous scheduling, Splunk can run a delayed search later while still evaluating the originally intended time range. This helps prevent backfill gaps , where an interval would otherwise never be searched because the scheduler was busy or the search could not execute on time.
This differs from real-time-oriented scheduling behavior, which prioritizes execution close to the current scheduled time and may skip older scheduled instances when resources are constrained. For security detections, that can be undesirable if the requirement is complete historical coverage rather than lowest possible latency.
This same principle aligns with the supplied study material ' s treatment of detection scheduling and late-arriving data: engineers must design search windows and scheduling behavior so events are not missed simply because indexing or execution occurs later than expected.
Study Guide topics: correlation-search scheduling, continuous scheduling, backfill, scheduler delays, detection coverage, late-arriving data.
