@chasmiller46, you are really on to the perfect solution here, IMHO. I started this rehash of this issue a week ago because the behavior of running the sequence changed depending on when you started the sequence, or even produced a strange sequence. If you started it before the start time of the first target, it would run one way, in my case #1, #2, #1, #3, which of course was not what I intended or would be expected. The reason it returned to #1 after finishing #2 is that it reevaluated the end time of #1 and now decided that it was in the future, which it was 2 hours ago, but should now be in the past when #3 should start, quite inconsistent, and the target had more frames to process, so it started it again.
Another common scenario for me is starting the sequence after 1 or more targets have already run and still have some additional frames to take, but finished because the end time came before finishing all frames. If I don’t explicitly uncheck the earlier finished targets, it would restart with them. It should still know that they have finished and those end times are now in the past,
A key element to add to your rules is:
The starting date should always be set to make target #1 start at a future date/time, unless that would cause the whole sequence to start more that 24 hours from now. The 24 hours may need to be shortened some. Then the sequence can be started any time during the evening and produce the same results for that period of time.
And if a necessary start or end time is not specified that these rules require, SGP could just make a reasonable assumption for the missing time.
And for me, reverting to using dates would be a disaster. They set of rules should work great for everyone.