tracker issue : CF-3928030

select a category, or use search below
(searches all categories and all time range)
Title:

Daily task w/o startDate gives a bad error

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Raymond Camden / Raymond Camden (Raymond Camden)

Created: 01/26/2015

Components: Scheduler

Versions: 11.0

Failure Type: Usability Issue

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Minor / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on September 06, 2019 using build 2016.0.01.298513 
Make a new task w/o a startdate:

		cfschedule(action="update", task="FirstTask", mode="application",
		interval="daily", url="http://localhost:8501/tests/scheduletests/one/task.cfm",
		starttime="13:00" );

The error is:

For input string: "daily"

And that's it. It needs to finish the error message.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3928030

External Customer Info:
External Company:  
External Customer Name: Raymond
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Hi Adobe and Ray, I see if startdate is specified, but starttime omitted, then a chained task is created. Interesting.. How about: - If startdate is specified, but starttime omitted, then starttime defaults to 00:00 - If starttime is specified, but startdate is omitted, then startdate defaults to now()? Thanks!, -Aaron
Comment by External U.
8790 | January 29, 2015 05:51:11 AM GMT
Big plus one on that Aaron. If you saw my blog post on it, this caused me trouble too.
Comment by External U.
8791 | January 29, 2015 09:22:12 AM GMT
+1 - That's definitely a bad/incomplete error message :) Also, startdate and starttime should have a default if one is specified w/o the other.
Vote by External U.
8801 | January 30, 2015 04:56:09 AM GMT
Hi Ray, I just saw your blog post. I agree startdate & starttime should be optional. I see, from your blog post, that you'd prefer startdate to default to tomorrow. I'd prefer it to default to today, but really I'm fine either way. Thanks!, -Aaron
Comment by External U.
8792 | January 30, 2015 05:28:00 AM GMT
Adobe, To clarify: When startdate & starttime are omitted, then chained task is created (good - b/c chained tasks don't run on a schedule, but rather are triggered by oncomplete="" of another task). When startdate is specified, but starttime is omitted, a chained task should not be created and an error should not be thrown. Instead, starttime should default to 00:00. When starttime is specified, but startdate is omitted, a chained task should not be created and an error should not be thrown. Instead, startdate should default to today (my preference) or tomorrow (Ray's preference) - either way, startdate should have a default in this scenario. Thanks!, -Aaron
Comment by External U.
8793 | January 30, 2015 05:38:56 AM GMT
This bug addresses three issues that need to be fixed. They are: 1. To give a proper error message when interval="daily" and startdate is not specified. 2. Chained task should not be created when startdate is specified and starttime is not. starttime should default to 00:00. 3. Chained task should not be created when starttime is specified and startdate is not. startdate should default to today.
Comment by Suchika S.
8794 | February 02, 2015 12:55:36 AM GMT
@Suchika Handled point 1. Rest 2 can cause backward compatibility issues, so avoiding them
Comment by Uday O.
8795 | September 25, 2015 01:52:26 AM GMT
Hi Uday, Currently, omitting startdate for a daily task throws exception. So, allowing startdate to default to today would not cause a backward-compat issue. So you're saying you will require startdate for a daily task, but if starttime is omitted then a chained task will be created? That doesn't make sense. Thanks!, -Aaron
Comment by External U.
8796 | September 25, 2015 02:05:45 AM GMT
Hi Uday, I was incorrect when I stated a chained task was created if daily task specified date w/o time. These throw the same error: cfschedule(action="update", task="dailyNoDate", interval="daily", url="http://www.coldfusion.com", starttime="00:00");//throws: For input string: "daily" cfschedule(action="update", task="dailyNoTime", interval="daily", url="http://www.coldfusion.com", startdate="9/25/2015");//throws: For input string: "daily" Thus: 1) If date is specified for daily task, then time can default to 00:00 2) If time is specified for daily task, then date can default to today There is no backward-compat issue then. Could you please confirm? Thanks!, -Aaron
Comment by External U.
8797 | September 25, 2015 02:41:57 AM GMT
@Aaron Makes sense But wont it be better if starttime defaults to current time if it is not specified rather than defaulting to 00:00?
Comment by Uday O.
8798 | September 25, 2015 04:03:50 AM GMT
Hi Uday, Ah, yes, you're right - that would be better. Good point! Thanks!, -Aaron
Comment by External U.
8799 | September 25, 2015 11:35:41 AM GMT
Hi Uday, One more note: Interval doesn't make sense for chained tasks. Thus, if interval is specified, then user is creating a non-chained task. In this case, startdate and starttime can both default to now. Right? Thanks!, -Aaron
Comment by External U.
8800 | September 28, 2015 03:47:39 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron
Comment by Aaron N.
31287 | September 06, 2019 12:16:28 AM GMT