18

Using the Task Scheduler in Windows Server 2008 R2 or Windows 2012, etc...

What is the difference between this setting:

Stop task if it runs longer than

and this setting on the same task:

Stop task if it runs longer than

Does one take precedence over the other? Do they conflict?

Improve this question
2

1 Answer 1

Reset to default
16

I have no authoritative reference but I have just tested the behavior of multiple different Stop conditions in Task Scheduler on both Windows 8.1, Server 2008 R2 and 2012 R2.

They both apply!

Whichever stop condition is met first, stops the task.

  • Per trigger stop condition: The Stop task if it runs longer than-condition specified in the Trigger will only apply when the task has been invoked by that particular trigger.

  • Per task stop condition: The Stop task if it runs longer than-condition specified for the Task (on the Settings tab) is global to that task, and will always apply, regardless of per-trigger stop conditions.

Example

Imagine a task with one trigger. If you have the per trigger stop condition set to 5 minutes, and the per task stop condition set to 30 minutes, you should expect the following behavior:

  • Task is invoked by the trigger -> Task stops after 5 minutes.
  • Task is invoked by you (via right-click and Run) -> Task stops after 30 minutes.
Improve this answer
4
  • Nice job testing this!
    – TheCleaner
    Jun 10, 2014 at 14:52
  • By stop do you mean it does taskkill /f /im executablename.exe ?
    – variable
    Jul 15, 2022 at 5:33
  • @variable Well, the task scheduler doesn't invoke taskkill.exe, but it calls a kernel API that does the same thing as taskkill, yes
    – Mathias R. Jessen
    Jul 15, 2022 at 9:23
  • So is it a stop or force stop?
    – variable
    Jul 15, 2022 at 9:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .