Redundant Cool Down Procedure on Abort

[3Duke3]

If a print job is started by selecting a file from usb, then immediately aborted (usually due to accidentally selecting the wrong file), the machine cycles through a lengthy cool down procedure, regardless of the print cores temperature at time of abort. The machine is locked and unresponsive until the cool-down procedure is completed, or if the machine is power cycled.

The problem is if you start a print job, and immediately abort it before anything has had a chance to reach any meaningful temperature, the cool down procedure redundantly invokes the continued heating of print cores until they reach a defined temperature, and then actively cools them back down before allowing you to start a new print job.

What should happen: If the print job is aborted before any material is extruded (or perhaps before cores reach a certain temperature), then no cool down procedure should be necessary, and the user can select a new print job immediately.

[3Duke3]

Have just noticed this doesn't happen every time. I need to investigate further but I suspect it may have some relation to weather or not the second extruder/hotend is required for the print job.