Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
Sounds reasonable enough here:… – TheCleaner Jun 10 '14 at 13:46
@TheCleaner Agreed ... testing as we speak :) – Mathias R. Jessen Jun 10 '14 at 13:58
up vote 14 down vote accepted

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.


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.
share|improve this answer
Nice job testing this! – TheCleaner Jun 10 '14 at 14:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.