tracker issue : CF-4202374

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

[ANeff] ER for: Scheduled Tasks page enhancements

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

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

Created: 05/11/2018

Components: Administrator, Administrator Console, Scheduler

Versions: 2018

Failure Type: Others

Found In Build/Fixed In Build: / latest build

Priority/Frequency: Normal /

Locale/System: / Platforms All

Vote Count: 1

Notes:
- Typically, all tasks need paused before installing CF updates or restarting CF. And currently-executing tasks need to finish.
- Typically, all tasks need resumed after installing CF updates or restarting CF.

Issue 1: Scheduled Tasks page doesn't have 'Pause All'/'Resume All' buttons.

Suggestion: Scheduled Tasks page could have 'Pause All'/'Resume All' buttons.

Issue 2: Scheduled Tasks page doesn't indicate which tasks are currently executing.

Suggestion: Scheduled Tasks page could display a red blinking dot (like PMT has for code profiler) in the "Last Run" column for tasks that are currently executing.

Screenshot attached. Using CF Admin is tedious to pause/resume 100+ tasks and it doesn't indicate which ones are currently-executing.

Attachments:

Comments:

Thoughts: 1) 'Pause All' / 'Resume All' buttons could be Standard Edition feature (b/c this feature would be simpler to introduce) 2) red blinking dot feature could be Enterprise Edition feature (b/c this feature is most useful when there are a lot of tasks, and will be more complex, and likely tie-into PMT API) Thanks!, -Aaron
Comment by Aaron N.
27772 | May 13, 2018 07:23:45 AM GMT
Aaron,I can see here that the main concern is to pause/resume all the tasks manually which can be time consuming if you have way too many tasks. But we can achieve this programmatically using simple scripts.  Either we can use LIST action to get all tasks and then pause/resume each of them Or we can use pasuseAll/resumeAll actions to pause/resume all tasks of given groups.  To know the current running tasks, we can make use of eventhandlers. In onTaskStart method we can add the task name in some struct and in onTaskEnd we can remove the name. At any time we can check this struct, all the tasks present in it would be in the running state
Comment by Uday O.
27818 | May 15, 2018 10:57:41 AM GMT
Hi Uday, Yes, thank you very much for the follow-up. I do have a similar solution already in place. I also tap into Admin API to abort any duplicate-fired tasks. I primarily filed this ER also for the benefit if CF's other customers - to smoothen the process of installing updates. No worries if Adobe wishes not to implement. Thanks!, -Aaron
Comment by Aaron N.
27831 | May 17, 2018 03:41:48 AM GMT
Workaround -  1) Use LIST action to get all tasks and then pause/resume each of them.  2) Use action="pauseAll|resumeAll" to pause/resume all tasks of a given group 3) use eventhandlers to know the status of currently running tasks. For example, in the onTaskStart method, add the name of the task in a struct and in the onTaskEnd method, remove the name. The struct can be checked art any given time to check the current list of tasks.  
Comment by Vamseekrishna N.
27854 | May 18, 2018 03:32:26 AM GMT
I find it very unfortunate to see this offered as a work-around. Could they write such code? Yes, some could. And I appreciate that you give tips to help them, but how many (in this situation) will know to find these suggested steps here? And should they have to bother? No. The proposal is for a UI button that facilitates someone easily (and quickly) pausing all tasks. It's a great idea for what is not an unusual situation. I'll offer just one (but there are use cases). I've helped many people who were moving to a new CF version and because they had their previous CF on the machine, they chose the option at the end of the installer to import the Admin settings. Often they didn't realize until it was too late that they now had tasks running on both CF versions. Having a simple "pause all" would be the perfect solution, and seems would be trivial to add, whereas it's too much to presume that each such person in a case like this would a) know how to do such scripting, b) want to bother, and c) could do it quickly, especially with the pressure of now having tasks running on both versions. Worse, I see that you have marked this "won't fix". Does that mean "no time to implement for CF2018"? That would be understandable, since public signs are that the prerelease is drawing to a close. But if "won't fix" means, "yeah, we don't see the need for this at all, ever", that I would argue strongly against. It's fairly trivial for you to add a button to do this for people (calling the very code you propose). Users simply should not have to do that. I hope you will reconsider.
Comment by Charlie A.
27870 | May 18, 2018 03:29:33 PM GMT
Hi Uday and Vamsee, Seriously? Customers upgrading or installing updates are not always the ones who know how to write CFML. C'mon, improve the product for your other customers? I could copy my code and send it to you? And the buttons are a no-brainer b/c that's just CSS. Sorry that I suggested an improvement idea. :/ Thanks!, -Aaron
Comment by Aaron N.
27874 | May 18, 2018 07:10:26 PM GMT
I'm just imagining the IT workers at a hosting company reading thru Adobe's workarounds above. I think their eyes would glaze over. =P Thanks!, -Aaron
Comment by Aaron N.
27875 | May 18, 2018 07:12:40 PM GMT
Aaron - The other option we have is to see how many users are interested in this change and then may be look at reconsidering. We've a good set of enhancements already lined up for post Aether. 
Comment by Vamseekrishna N.
27922 | May 23, 2018 08:17:14 AM GMT