My schedule stops after the first command — how do I add multiple tasks?
If your schedule seems to run one command and then stop, it is almost certainly a setup issue rather than a bug. A single schedule can run a whole sequence of tasks — you just need to add them the right way. This article explains how.
How schedules run tasks
A schedule in the Schedules tab runs a sequence of tasks, one after another. The key point: the extra steps must be added as additional tasks within the same schedule, not as separate schedules.
Chain multiple tasks correctly
- Open the schedule in the Schedules tab.
- Add each additional step as a new task in the same schedule — do not create a separate schedule for it.
- Give each task a small time offset/delay so they run in order rather than all at once (for example: send a warning command, wait, then restart).
- Confirm the schedule is enabled and that each task's action is set correctly.
Tip: A common working pattern is: task 1 broadcasts "Restarting in 60s", then a delayed task 2 issues the restart. The offset is what makes the sequence flow.
Frequently asked questions
Why did it stop after the first command? The follow-up step was probably placed in a separate schedule, or given no delay so it never ran in sequence. Add it as another task inside the same schedule with a time offset.
How do I add a delay between tasks? Each task has a time offset/delay setting. Set a few seconds (or more) on later tasks so they fire after the earlier ones complete.
Do the tasks run top to bottom? Yes, in sequence, respecting the offsets you set. Make sure the ordering and each action are correct.