tracker issue : CF-3218423

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

Migrated scheduled tasks show incorrect information

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Rob Kolosky / Rob Kolosky (rkolosky)

Created: 06/19/2012

Components: Scheduler

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / 283376

Priority/Frequency: Normal / Few users will encounter

Locale/System: English / Windows 7 SP1 64-bit

Vote Count: 0

Problem Description:

I have a scheduled task that was migrated from Cold Fusion 9 to Cold Fusion 10. Existing code looks for the scheduled task, and if required, re-schedules the task for the next run time. When going into the Administrator, the Scheduled Task dashboard incorrectly shows the last run as "Not Run" and the next run as "Expired" when they are actually defined. The scheduled task does actually run at the time specified.

Steps to Reproduce:

Migrate a scheduled task from Cold Fusion 9
Run code to re-schedule the task for 5 minutes in the future:
<cfset targetDate = DateAdd("n",5,Now()) />
<cfschedule action="update" task="Process Ingenium Files" interval="once" operation="HTTPRequest" url="http://#cgi.http_host#/lmsAdmin/index.cfm?action=main.processFiles" startDate="#DateFormat(targetDate,"mm/dd/yyyy")#" startTime="#TimeFormat(targetDate,"hh:mm:ss tt")#" />
Login to the Administrator -> Server Settings -> Scheduled Tasks

Actual Result:

See that the Administrator lists the task's last run as "NOT RUN" and the next run as "EXPIRED"

Expected Result:

It should list the last time the scheduled task ran, and what the next scheduled run is, if it has been defined.

Any Workarounds:

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

Watson Bug ID:	3218423


External Customer Info:
External Company:  
External Customer Name: rkolosky
External Customer Email:  
External Test Config: My Hardware and Environment details: Windows 7 Pro, x64, 12 GB RAM, IIS, Chrome


  1. June 19, 2012 00:00:00: 1_bad_scheduler_display.jpg


Last_Run will and should become "NOT RUN" after every updation of the task because it's a completely new task now. Giving the Last_Run time of the task (which was before the updation) will make things ambiguous. (especially if the interval or url has changed) However next_run showing as EXPIRED is a bug and we are fixing it.
Comment by Himavanth R.
18973 | November 21, 2012 03:31:02 AM GMT