What a scheduled task does when Haruno was closed or the PC was asleep at its time, when two tasks want to run together, when a run fails before it starts, and how to read the run history.
Mac appAvailable
Windows appAvailable
A scheduled task runs only while Haruno is open. This page explains what happens around a run: times that were missed, runs that wait their turn, and runs that fail and are tried again. Each task's Run history shows the result.
The run history
Every row in Run history has a time and a status. The time is the time the run belonged to, not when it finished.
Status
What it means
Executed
The run finished.
Failed
The run ended in an error. The row says which.
Cancelled
You pressed Stop, or Haruno was closed while it ran.
Skipped (app closed)
A time passed without a run.
Skipped (already running)
A time came while the same task was still running.
Rows are listed newest written first, so read the times, not the order. Each task keeps its latest 50 rows. Open transcript on a row opens the chat the run had.
A run that started two minutes or more after its time says so, for example Executed · started 12 min late. Waiting in the queue counts toward that.
When Haruno was closed or the PC slept
Haruno looks at each task's schedule and finds the times that passed without a run. This covers a closed app, a PC that slept and a clock that jumped forward. Then:
The most recent missed time runs once. It runs as soon as Haruno notices, when it starts or when the PC wakes.
Every older missed time gets a Skipped (app closed) row. An hourly task left for a week gets one run and many skipped rows, not a run for every hour.
A task that is Off gets nothing for the time it was off.
Turning a task back on, or saving it with a new schedule, starts counting from that moment. Old times are not shown as missed.
One run at a time
Haruno runs one scheduled run at a time. Scheduled times, catch-up runs, retries and Run now all wait in the same line. A task that is waiting shows Waiting for another task… instead of Running…. You can still press Stop on it, but Run now and Delete are unavailable until it finishes.
If a time comes for a task that is still running, that time is recorded as Skipped (already running) and no second run starts.
Tries again after a failure
If a run fails before it got any answer, for example because the network was down, Haruno tries again. It does not try again when you pressed Run now, when the run timed out or was stopped, when its folder was missing, when the service refused the request (for example, you are signed out or your plan has no allowance left), or when the run already did some work.
The retries come 5 minutes, then 15 minutes, then 30 minutes after the one before. Each attempt is its own Failed row. It ends with what happens next:
Haruno will try again at 14:20.
Haruno tried again three times and will wait for the next scheduled time.
The time is in your PC's time zone. If the next scheduled time comes first, the retry is not planned, and the task runs at that time as usual. Closing Haruno forgets any retry that was waiting.
When the time zone changes
A task's schedule is read in your PC's time zone. If you travel or change the zone while Haruno is open, the schedule follows at once. The next run, the run history and the preview of next runs all show the new zone. If you move forward past a task's time, that time counts as missed, and the rule above runs it once.
What to tell a customer
If a task did not run when they expected, open its Run history. A Skipped (app closed) row means Haruno was not running at that time. Turning on Launch at startup fixes most of these.