tracker issue : CF-3933576

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

[ANeff] ER for: <cfschedule action="list"> to return NextFire

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 02/04/2015

Components: Scheduler

Versions: 2016,11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win All

Vote Count: 0

CF Admin's Tasks page displays a "Next Run" column. This ER is to add that timestamp (or NULL if the task expired) to the <cfschedule action="list"> result query as "NextFire".

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

Watson Bug ID:	3933576

Reason:	NewBug

External Customer Info:
External Company:  
External Customer Name: Aaron
External Customer Email:



Per CF-3934370, Admin API's findTask(): 1) returns NextFire if task was created via CF Admin 2) does not return NextFire if task was created via <cfschedule> Of course, <cfschedule action="list"> should return NextFire in both cases. Thanks!, -Aaron
Comment by External U.
8603 | February 04, 2015 08:14:34 PM GMT
Can you please specify a strong use-case for this?
Comment by Vamseekrishna N.
8604 | August 18, 2015 10:43:44 PM GMT
Hi Vamseekrishna, There are 2 use cases for knowing a task's "NextFire": 1) Management wants to know when reports will be auto-generated. These reports are auto-generated by scheduled tasks. And some tasks' interval can change dynamically based on other criteria. So it is useful for management to see a page that shows them the current report auto-generation schedule (based on NextFire). 2) Some tasks should not run simultaneously. So, a 'handler' task runs every 10min and determines if certain tasks are about to run (based on NextFire). If yes, then other tasks are paused. If no, then other tasks are resumed (if the 'handler' task had previously paused them). So, yes, "NextFire" is *very* useful. Admin API's findTask() already knows the NextFire - if the task was created via CF Admin. It should also know the NextFire if the task was created via <cfschedule>. And, more importantly, <cfschedule action="list"> should actually return the NextFire. Admin API shouldn't be required just to know when the task will fire next. I hope you can please consider. Thanks!, -Aaron
Comment by External U.
8605 | August 23, 2015 04:20:02 AM GMT
Hi Adobe, The 2 use cases in my previous comment are very much real and still exist. Knowing task's NextFire is very important. I hope you can please consider. Thanks!, -Aaron
Comment by Aaron N.
8606 | July 30, 2017 08:44:06 AM GMT
Hi Adobe, I see the Status changed to "To Fix". Thanks very much! Is fix planned for both 1) Admin API -and- 2) <cfschedule action="list">? I'm most interested in #2, but both should work. Thanks!, -Aaron
Comment by Aaron N.
8607 | August 03, 2017 08:22:02 AM GMT
We will evaluate both the use-cases.
Comment by Vamseekrishna N.
8608 | August 03, 2017 09:15:21 AM GMT
Hi Vamsee, Thanks very much!! -Aaron
Comment by Aaron N.
8609 | August 03, 2017 06:03:17 PM GMT