Quoting from http://docs.splunk.com/Documentation/Splunk/6.1.1/Report/Configurethepriorityofscheduledreports:
Continuous scheduling is used for situations where problems arise when there's any gap in
the collection of report data. In general this is only important for reports that populate
summary indexes, though you may find other uses for it. When a report is enabled for
summary indexing, Splunk Enterprise changes its scheduling option to continuous
automatically.
When you see a "status=continued" event it refers to the case where a continuous search that was supposed to run at a given time wasn't and the system will come back to it later.
Quoting from http://docs.splunk.com/Documentation/Splunk/6.1.1/Report/Configurethepriorityofscheduledreports:
Continuous scheduling is used for situations where problems arise when there's any gap in
the collection of report data. In general this is only important for reports that populate
summary indexes, though you may find other uses for it. When a report is enabled for
summary indexing, Splunk Enterprise changes its scheduling option to continuous
automatically.
When you see a "status=continued" event it refers to the case where a continuous search that was supposed to run at a given time wasn't and the system will come back to it later.
So should we expect in the scheduler log that there will be a status completed for the specified scheduled time?
Yes there will be a status completed.