Why a scheduled AI task is not running in Mono
Diagnose missing task runs, local scheduling, time changes, failed steps, and notification issues in Mono with a simple manual test.
When a scheduled task seems to have stopped, ask three questions first: did it start, did it finish, and did you get a notification? Each answer points to a different fix.
Mono Tasks run on your device, not on an always-on server, and your phone’s system can pause apps in the background. This guide helps you find out why a run is missing without creating duplicate actions. Mono isn’t out yet; you can join the waitlist.
1. Check the recorded runs first
Open Tasks and look at the task’s past runs. Check the time, whether the run succeeded or failed, and the result of each step. A notification is useful, but the run history is better evidence of what really happened.
A successful run with no notification is a notification problem. A failed run is a problem in the task itself. No run at all points to the schedule, the device or the setup.
Only the most recent runs are kept, and clearing past runs removes them all. So if a notification opens a run that is no longer available, that doesn’t mean the task never ran. If the task changes something in another service, check there too. Don’t tap Play again and again while you’re unsure what happened.
2. Confirm the schedule and local time
Check that the task is turned on and that its schedule isn’t Manual. Mono offers hourly, daily, weekday and weekly schedules. Look at the actual time and days instead of trusting the task’s name.
Tasks follow your device’s clock. After travel or a clock change, compare the schedule with the device’s current date, time and weekday.
To test, pick a time a few minutes ahead while you can keep the app open. A task you create after today’s time has already passed won’t run for that earlier time. Write down the planned time before the test, so you can tell a late run from a different schedule.
3. Understand device availability and catch-up
Tasks run while Mono is running on your device. If Mono is still waiting for you to finish setting up or linking the device, do that first.
When your device was off or Mono was closed, a missed task catches up the next time you open the app. It doesn’t replay every hourly slot you missed, so several hours offline don’t mean several runs are waiting.
On iPhone and iPad, the system can give Mono a little background time to finish work that has already started, but it won’t keep starting new tasks indefinitely. If something must run at an exact time even when all your devices are off, use a service built for that.
4. Run one controlled manual test
Tap Play once, with a small input or a harmless destination. Check the steps and any effect outside Mono. This tests the task without waiting for its next scheduled time.
| What you see | What to check next |
|---|---|
| Manual run also fails | Inputs, account sign-in, network, and the failing step |
| Manual run works, scheduled run missing | Task turned on, schedule, local time, device availability |
| Run works, no notification | Mono’s task notification setting and the system permission |
| Output appears twice | Run history and the destination before another retry |
A manual run counts as a run. If you start one after today’s scheduled time has passed, Mono treats today’s run as done. Watch for the next scheduled time instead of expecting another run straight after your test.
5. Fix the failing step before retrying
A failed run counts as a run too, so Mono won’t retry it on its own before the next scheduled time. Use the step results to fix the specific problem, then retry on purpose.
For example, an expired account connection needs you to sign in again; changing the schedule won’t fix it. An empty input needs a plan for the empty case. A step that uses the internet needs that service to be reachable.
If a task has several steps, one failure doesn’t stop the rest, and a later failure doesn’t undo earlier steps. Check the destination for a newly created item before you retry a task that could create another one.
6. Confirm the next scheduled result
After a successful manual test, leave the task on and watch one future scheduled run while the app is available. Compare its time and output with the manual run.
If it runs early or twice, turn the task off and check the destination before you try again.
If you need help, note the task’s schedule, the device’s time zone, whether the app was open, the run time and the failing step. Leave out private inputs and passwords. Use the reliable automation guide to simplify a fragile task, or check a newly created task before you schedule it again.
