cfschedule

With respect to CFSCHEDULE, if one wants to set an interval of recurrence other than the offered "daily, weekly, or monthly" options, there is a way to go that (for CF9, at least, not for CF10), though it's not documented. You can use the tag's INTERVAL attribute to specify pretty much any recurrence timeframe, at least in seconds.

For instance,to setup a bi-weekly interval, you just need to set the number of seconds appropriately: 1209600 (24*60*60*14). When viewed in the CF 9 Admin, you'll also see this populated in the "daily every" field as a value of equivalent hours: 336 (24*14). The value for bimonthly is 5184000 (1440 hours in the Admin), while the value for quarterly is 7776000 (2160 hours in the Admin).

Sadly, values beyond a single day (24 hours) are not accepted in the admin interface, so while you can create such larger value with the tag, and it will appear in the Admin, this limitation does mean that you will not be able to edit a task created this way.

Also, as of CF10, you can't even specify the INTERVAL in the tag to be greater than a day (in seconds). Instead, you will need to use the new crontime attribute in the tag, or crontime field in the interface.

Message was edited by: Charlie Arehart Updated to clarify that while the tag lets you create an interval longer than a day (in CF9), and it shows in the Admin interface, you cannot then edit the task.

It is not stated in the description of the tag that the startTime and endTime parameters always refer to the time the task starts and runs on each and every day of the defined schedule period. This is perhaps unnecessary for interval values of 'daily', 'weekly' and 'monthly' but it is not at all obvious, or even to be suspected, for intervals of less than a day expressed as a number of seconds. On the basis of the information provided, you would expect that a task set to run every five minutes starting a 09:00:00 today (or any other time) would run every five minutes thereafter until the endDate and endTime, or forever if these were not specified.

Also, if the endTime is not specified, the scheduled task does not stop at the end of each day, but after the first time the task runs in the following day. For example, a task with a startTime of 15:59:59 and an interval of 14,400 seconds (4 hours) will run at 19:59:59, at 23:59:59 and again at 03:59:59 the next day before stopping to wait for 15:59:59 to roll around again. While this may be of little importance in many cases, it in fact caused me some grief. In any event, the functionality should be known and specified in detail, not left to the user to discover by trial and error.