From Newsgroup: alt.comp.os.windows-11

Hi All,

W11-25H2 V2

I was working a a task that a customer wanted run
from the Task Scheduler. Every time I tested
is said "running". It should have exited almost
instantly.

I tore my hair out trying to figure out why is never
exited. Turns out, all I had to do was press "F5"
to refresh the Task Scheduler screen. My code way
fine!

HTH some else,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Serious error.
All shortcuts have disappeared.
Screen. Mind. Both are blank.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T <T@invalid.invalid> wrote:

W11-25H2 V2

I was working a a task that a customer wanted run
from the Task Scheduler. Every time I tested
is said "running". It should have exited almost
instantly.

I tore my hair out trying to figure out why is never
exited. Turns out, all I had to do was press "F5"
to refresh the Task Scheduler screen. My code way
fine!

After running a scheduled task, Task Scheduler does not automatically
refresh its display nor refresh when status of a task changes. You run
a task, refresh, and then check status.

menu: Action -> Refresh
Actions panel -> Refresh
F5 also works.

Commands to services are asynchronous: Task Scheduler, or sc.exe, issue
the command, but there is no response from the service for the Task
Scheduler to trigger upon to know the service's state has changed. When
Task Scheduler issues a state change, it doesn't wait and report a state change, because service didn't report the state change hence Task
Scheduler (or sc.exe, the service controller) are asynchronous to the
effect of the commands they sent to the services. That's why you have
to be careful when bringing up some services that you do so in the
correct order, and refresh to see when the dependent services are ready.

The services do not issue a semaphore or signal when they've changed
state. The Task Manager won't know until it polls the service, and
that's done on a refresh.

Been that way for a very long time. Probably back through all NT-based versions of Windows. Commands are asychronous to the service state.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T wrote:

I was working a a task that a customer wanted run
from the Task Scheduler.-a Every time I tested
is said "running".-a It should have exited almost
instantly.

Task Manager doesn't auto-refresh the status, you have to use F5.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 4/30/26 01:34, Andy Burns wrote:

T wrote:

I was working a a task that a customer wanted run
from the Task Scheduler.-a Every time I tested
is said "running".-a It should have exited almost
instantly.

Task Manager doesn't auto-refresh the status, you have to use F5.

It sure seemed to on many of the other things I was testing.

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T wrote:

Andy Burns wrote:

Task Manager doesn't auto-refresh the status, you have to use F5.

It sure seemed to on many of the other things I was testing.

It may do it on a longish interval, but not reliably ...

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Thu, 30 Apr 2026 12:26:03 +0100, Andy Burns wrote:

T wrote:

Andy Burns wrote:

Task Manager doesn't auto-refresh the status, you have to use F5.

It sure seemed to on many of the other things I was testing.

It may do it on a longish interval, but not reliably ...

The task may perform on data that the customer kept adding, which of course, lengthen the time for the task to complete each time more data is added.

Did the custom don't think that, more data require more time to process?
Or does the customer not aware that, the data grows bigger over time?

Or maybe the storage performance has decreased due to its age?
--- Synchronet 3.21f-Linux NewsLink 1.2