...
In case of different time zones defined on different sub-sequences the result is undefined and may vary with implementation.
Extended time sequence definition syntax is implemented. Now you can specify a sequence like
[2015.MAY.25.14.30min..2015.MAY.26.16/hour]
Which will result in
<ExecuteStatus>
<Result Trigger="1:1=Mon May 25 14:30:00 PDT 2015"/>
<Result Trigger="2:2=Mon May 25 15:30:00 PDT 2015"/>
<Result Trigger="3:3=Mon May 25 16:30:00 PDT 2015"/>
<Result Trigger="4:4=Mon May 25 17:30:00 PDT 2015"/>
<Result Trigger="5:5=Mon May 25 18:30:00 PDT 2015"/>
<Result Trigger="6:6=Mon May 25 19:30:00 PDT 2015"/>
<Result Trigger="7:7=Mon May 25 20:30:00 PDT 2015"/>
<Result Trigger="8:8=Mon May 25 21:30:00 PDT 2015"/>
<Result Trigger="9:9=Mon May 25 22:30:00 PDT 2015"/>
<Result Trigger="10:10=Mon May 25 23:30:00 PDT 2015"/>
<Result Trigger="11:11=Tue May 26 00:30:00 PDT 2015"/>
<Result Trigger="12:12=Tue May 26 01:30:00 PDT 2015"/>
<Result Trigger="13:13=Tue May 26 02:30:00 PDT 2015"/>
<Result Trigger="14:14=Tue May 26 03:30:00 PDT 2015"/>
<Result Trigger="15:15=Tue May 26 04:30:00 PDT 2015"/>
<Result Trigger="16:16=Tue May 26 05:30:00 PDT 2015"/>
<Result Trigger="17:17=Tue May 26 06:30:00 PDT 2015"/>
<Result Trigger="18:18=Tue May 26 07:30:00 PDT 2015"/>
<Result Trigger="19:19=Tue May 26 08:30:00 PDT 2015"/>
<Result Trigger="20:20=Tue May 26 09:30:00 PDT 2015"/>
<Result Trigger="21:21=Tue May 26 10:30:00 PDT 2015"/>
<Result Trigger="22:22=Tue May 26 11:30:00 PDT 2015"/>
<Result Trigger="23:23=Tue May 26 12:30:00 PDT 2015"/>
<Result Trigger="24:24=Tue May 26 13:30:00 PDT 2015"/>
<Result Trigger="25:25=Tue May 26 14:30:00 PDT 2015"/>
<Result Trigger="26:26=Tue May 26 15:30:00 PDT 2015"/>
<Result Trigger="27:27=Tue May 26 16:30:00 PDT 2015"/>
</ExecuteStatus>
As you can see, sequence interval boundaries can now be hierarchical in dot-delimited format e.g. 2015.MAY.25.14.30min means 2015-May-25:14:30. It is not necessary to specify time units on each element as long as there is at least one and you follow the standard time interval hierarchy (i.e. year-month-day-hour-minute-second-millisecond). In the above example, “MAY” is used by the system to match all the numerals with time units (i.e. it recognizes that if MAY is a month then to the left of it must be the year and to the right must be day, hour, minute etc.). For non-standard definitions, you can always specify time unit explicitly (e.g. 2015yr.128doy.15hr, where 2015 is a year, 128 is day of the year and 15 is hour of the day). Only 24 hours format is currently supported.