Very good question without a great answer. This feature wasn't particularly well-defined, so we have some room to adjust it as we see fit. For now I think it does a reasonable job of preventing a rogue task from ruining the system over and over. For a case like sync with auto-publish, I agree that it would be valuable for this tracker to follow spawned tasks. There would be additional complexity in that currently we don't report why a schedule was disabled except it hit the failure threshold, and this could lead to confusion if a user can't find any evidence that the scheduled task failed (because it was a sub-task that failed). I think this is a good idea that I'd rather implement later, when we have a more mature concept of sub-task state tracking, and time to improve this feature's reporting.