Task Scheduler says Ready but the task never ran: 3 silent causes on Windows

Windows Task Scheduler said "Ready" but my task never ran: three silent misses I found

"Ready" in Windows Task Scheduler only means the task is registered. It doesn't mean the task ran. I learned that from a monthly alert that had never been sent once since I set it up, while its status said Ready the whole time. Between July and September I found three different ways a task can sit there looking fine and do nothing: a date check that only lined up about once every seven months, a reboot that left the PC on but nobody logged in, and a pair of escaped quotes that killed a task the moment it started.

If you only need the checks, skip to "How I check whether a task really ran." The rest is how each one hid.

By L

Contents

  1. Miss 1: a monthly alert that fired zero times
  2. Miss 2: the PC was on, but nobody was logged in
  3. Miss 3: two escaped quotes, instant death
  4. How I check whether a task really ran
  5. What I check now
  6. FAQ

Miss 1: a monthly alert that fired zero times

The alert was meant to go out once a month, on the 1st. The script I used to register tasks (PowerShell) had no monthly trigger, so the setup became a weekly trigger on Mondays, plus a line at the top of the script that said: if today isn't the 1st, exit.

So the script only got past that line when the 1st of the month was also a Monday. That happens roughly once every seven months. In the time the alert had been deployed, there was exactly one such month.

And even that one run wouldn't have reached me. The alert sent its message through a webhook address that had never been put in my settings file, so every run stopped early with a warning.

I found the problem by checking the lock files. My daily jobs leave a small lock file when they run. The folder had 135 lock files from the daily jobs and zero from the monthly one.

I deleted the date check. The task now runs on the first Monday of each month, and a monthly lock file makes sure it runs only once. I also pointed it at my single notification script, and deleted the dead webhook path instead of keeping it as a fallback.

Miss 2: the PC was on, but nobody was logged in

One morning in July, four of my morning automations didn't run: three briefings and one other job. Nothing in Task Scheduler looked broken.

Windows Update restarted the PC at 06:33. I logged in at 09:09. My morning tasks were set to run only when I'm logged in, so every scheduled time between those two moments was skipped without a word.

The tasks had "Run task as soon as possible after a scheduled start is missed" turned on. On my PC, that setting only caught up runs missed while the PC was off. It did nothing for runs missed while the PC was on and sitting at the login screen.

My watchdog, which checks whether the morning jobs ran, sent an alert at 09:40. (I wrote about that daily check in my post on a Python script that failed in Task Scheduler.)

I added a small catch-up task that runs two minutes after I log in. It looks at a fixed list of 9 tasks. For each one, if today's scheduled time has already passed and the task's last run is from before that time, it starts the task. There's no AI in it, just a check and a start.

Miss 3: two escaped quotes, instant death

My Saturday weekly task failed on July 4 and again on July 18, each time right after it started. The result code was 0xFFFD0000. Task Scheduler can also show the same value as the negative number -196608.

The cause was in how the task had been registered. The Arguments field contained escaped quotes (\") around the script path. Task Scheduler passed those along, PowerShell couldn't find a script with that name, and the task ended immediately. I registered it again with plain quotes, and a test run returned 0.

This one needs a confession. Before I found the quotes, I had blamed that same -196608 on a different problem, a fake python from the Microsoft Store, in my Python post. That fake python was real and worth fixing, but it wasn't behind this code. I've added a correction to that post.

Right after registering a task, I now read back what Windows saved:

(Get-ScheduledTask -TaskName "YourTaskName").Actions

In my case, the escaped quotes in that field were enough to make the task fail while its status still said Ready.

How I check whether a task really ran

What I look atQuestionWhat "really ran" looks like
Something the task producesIs there a lock file, log line or message from today's run?A fresh file or line with today's time
Get-ScheduledTaskInfo LastRunTimeDid the last run happen at or after the last scheduled time?LastRunTime at or after the scheduled time
Restart time vs. login timeWas the PC restarted before my login on a day with misses?No scheduled time falls between the two
(Get-ScheduledTask).ActionsDoes the saved path have stray escaped quotes?The exact path I meant
The trigger and any date checks in the scriptCan the trigger and the script's own conditions both be true on the same day?Yes, on every day I expect it to run

When a morning job goes quiet, I go in this order: did the watchdog alert, what does LastRunTime say, then compare the restart time with my login time. For the restart time I look at the Windows event that records shutdowns and restarts (event ID 1074).

What I check now

I used to rely on the status column. Now I check the files, logs or messages a task leaves behind.

Before I build a new job on top of an existing automation, I also check that the existing one has actually run recently. If it's dead, a job attached to it dies with it.

FAQ

Why does Task Scheduler say Ready when my task never runs?
Ready means the task is registered and waiting for its trigger. It says nothing about whether past runs happened or worked. Check LastRunTime and something the task produces.

Does "Run task as soon as possible after a scheduled start is missed" catch every missed run?
Not on my PC. It caught runs missed while the PC was off. Runs for a task set to run only when I'm logged in were skipped while the PC was on but at the login screen. I added a catch-up task that runs after login.

What does result 0xFFFD0000 (-196608) mean for a PowerShell task?
In my case, PowerShell couldn't find the script because the Arguments field had escaped quotes around the path. After I re-registered the task with plain quotes, a test run returned 0. Read back (Get-ScheduledTask).Actions to check yours.

How do I run a task monthly if I only have a weekly trigger?
Don't combine a weekly trigger with "exit unless it's the 1st." With a Monday trigger, the script only gets past the date check when the 1st falls on a Monday. I run it on the first Monday and use a lock file so it runs once per month.

Comments

Post a Comment

Popular posts from this blog

Python script works manually but not in Task Scheduler: the Microsoft Store python stub (and a daily alive check)

Image
My Python script ran perfectly when I started it by hand. My weekly publish job had produced nothing for 3 weeks, and I got zero error messages. On July 7 I found one problem: the scheduled task called plain python , which in the scheduler's environment resolved to the Microsoft Store stub. That fake python.exe did no work and exited. I replaced python with the full path to the real interpreter. Then I added a daily "I'm alive" message so the next silent failure can't hide for weeks. Correction (October 17, 2026): The first version of this post said the Saturday task's result code, -196608, came from the Microsoft Store python stub. My later repair notes show that code came from escaped quotes in the task's settings. The stub problem below was real, and I fixed it, but it wasn't behind that code. Details are in the "A second cause" section. If you only need the fix, jump to "The one-line fix" below. The rest is how I found it ...
Read more »

Schedule a weekly AI summary with Windows Task Scheduler (with a human OK step)

Image
My AI assistant had one big weakness: it does nothing until I open it. Every Sunday night I was supposed to ask it to summarize my week, and I forgot more often than I remembered. Windows Task Scheduler fixed the forgetting part. At 10 pm every Sunday, Windows runs a small PowerShell script that drops a signal file and notifies me. The AI does not run at 10 pm. The next time I open a session, the AI sees the signal file and tells me a weekly job is waiting. I press OK, and only then does it do the work. During my 14-day trial, my first approach failed and I ran into two bugs in the first week. I also added three guardrails. I call the whole setup "Jarvis." Everyone names their assistant, and I'm no exception. By L Contents Attempt 1: telling the AI "run at 10 pm on Sundays" (failed) What worked: queue the job from the OS Why a human still presses OK Week 1, bug 1: the PC was off Week 1, bug 2: it fired twice A minimal version of the setup The test on my real...
Read more »

Codex vs Claude Code: which jobs I give each (3 months of work logs)

Image
I use Codex and Claude Code for different jobs. Between July 17 and October 16, 2026, my AI work log got 442 lines. Claude Code's models appear on 314 of them, mostly building and writing. Codex appears on 90, and 80 of those were in the reviewer role. Scripts with no AI took 18 lines, and 20 lines have no model name (10 of them are no-model steps marked "none"). By default, a model from the other company reviews the work. If you only want the setup, jump to "My routing table." The rest is the reasoning and what the log says. By L Contents Why a second company What the 442 lines say My routing table When one of them runs out If you're starting with one tool FAQ Why a second company I'm not a developer. I describe what I want, and the AI writes the code, runs the commands and writes the documents. That means I can't always tell when a result is wrong. A broken screen is easy to spot. A wrong number in a correct-looking table is not. My reason...
Read more »

What not to automate with AI: my approval rule for money and irreversible actions

Image
I let AI handle all of my reading, summarizing and analysis automatically. I let it create and edit files too. But anything that spends money or publishes something to the outside world still waits for me to press approve. I decide where a task goes with two questions: if this goes wrong, does money leave my account? And can I undo the result? If a mistake could cost money, or the result can't be undone, the task needs my approval before it runs. That line hasn't moved since I drew it. What did change was how I approve things. I built a one-tap approve button for my phone, and I took it down myself 26 days later. That story gets its own post. This one is about the line itself. By L Contents The worry that grew as the AI got better Why "just send me a notification" wasn't enough What my approval step looked like The line you can draw today Common questions The worry that grew as the AI got better I had already split my AI helper into three roles: planning, d...
Read more »

Telegram bot receives /start automatically: how it triggered my kill switch (one-line fix)

Image
I opened my Telegram bot's chat, tapped Start , typed nothing else, and my bot executed "release" on its emergency stop. I found that Telegram sends /start to the bot when you first open its chat and tap Start . One of the words I had mapped to my "release" command was from the start family, so that automatic /start was read as "release." I fixed it in one line by removing every start-family word from commands that change state and keeping /start for a usage message only. By L Contents The setup: a 3-second emergency stop on my phone The symptom: "release executed" in the log The cause: Telegram's automatic /start Reproduce it in 5 minutes The one-line fix 3 kinds of commands that should never share a word with /start Checklist: safe bot command design What I took from it FAQ The setup: a 3-second emergency stop on my phone I hand money-related chores to a few AI assistants. One assigns work, one processes it, and one checks the r...
Read more »