Checking that it ran

Every firing leaves a record, and the instance screen keeps that history beside the task itself. One line per firing: when it was due, when it actually started, how long it took, whether the schedule or a person started it, and how it ended.

Open a line to see what the run produced. For cycle counting that is how many cells came up due and how many count documents were made from them — which is the answer to "why are there no documents this morning": either nothing was due, or the documents already existed, or the run reached the limit you set for it.

How a run ends

A run that did its work ends Succeeded. Short of that it may still be waiting its turn, may be running, may have done part of the work, may have failed, or may have been skipped — and in the last two cases the history names the reason.

A due time is not a promise of the exact minute, which is why the history records both when a run was due and when it began. And if the system was unavailable when a run was due, the run is not lost — it is carried out later, and the history marks it as one that caught up.

Running it now

Run now fires the task immediately, without waiting for the schedule. The app asks you to confirm and says plainly that once started the run cannot be called back. From there it goes exactly the way a scheduled run goes, and it appears in the history as started by you — which makes it the sane way to test a new task instead of waiting until eight in the morning.