Title:
onMisfire attribute of cfschedule docs & tag behavior don't match & include duplicate arguments (fire_now vs. firenow)
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Rob Bilson / Rob Bilson (Rob Bilson)
Created: 11/09/2012
Components: Scheduler
Versions: 10.0
Failure Type:
Found In Build/Fixed In Build: Final /
Priority/Frequency: Normal / Most users will encounter
Locale/System: English / Windows 7 64-bit
Vote Count: 0
Problem Description:
According to the documentation (http://help.adobe.com/en_US/ColdFusion/10.0/Developing/WSe61e35da8d31851899e53a51353e870493-8000.html), the onMisfire attribute of the cfschedule tag supports the following options:
onmisfire="FIRE_NOW,NOW_EXISTING,NOW_REMAINING,NEXT_EXISTING,NEXT_REMAINING,INVOKEHANDLER....
To make things more confusing, if you pass a bogus option to the tag to see what the error message returnsm it gives you the following:
The specified value is not supported for onmisfire and valid options are: invokehandler, firenow, fire_now.
Notice that fire_now and firenow are both allowed. Other CF documentation seems to indicate that fire_now is the correct value as does the code behind the ColdFusion Administrator for scheduled tasks. In any case, the CF team needs to update the documentation to reflect the correct parameters, and a future updater needs to remove the incorrect argument (firenow).
Steps to Reproduce:
Actual Result:
Expected Result:
Any Workarounds:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3363329
External Customer Info:
External Company:
External Customer Name: Rob Brooks-Bilson
External Customer Email:
External Test Config: My Hardware and Environment details:Attachments:
Comments: