FFCore Hot Folder routing rules

[CJ]

Thank you for the response. Unfortunately that does not resolve the issue. Prior to 6.2 upgrade all jobs in paused state were failed if the server was rebooted which it dawns on me now is why i was able to update the routing rules within the Hot Folder after a reboot. Now in 6.2 i've got that set to not fail the jobs in Core Configure. Apparently it is in fact these held jobs the system is viewing as in progress for the Hot Folder and won't allow the folder to be edited while it has what it considers active jobs. Concerned on how to get around this as the output que (paused jobs) is never going to be empty. In Process Manager you could simply pause the hot folder at anytime but Core doesn't seem to have this functionality.

[DavidU54339-XRX]

The FreeFlow Core service can be stopped/started in Services -- see below.

[CJ]

In FFCore when trying to add a new routing rule to an existing hot folder FFCore errors out. Unable to update hot folder "XWF_HotFolder"... There is an error in the hot folder location. The hot folder may not exist in the specified path, or the path is entered incorrectly. Ensure that the hot folder location exists, and enter the correct path to it. The only way i've found to get around this is to reboot the entire server and make changes before all the services are functioning again. Is there a trick to this, a Core service that can be stopped and restarted? For reference, we are on FFCore 6.2 and this issue has existed in every iteration since we installed @ 5.xx. The hot folder in question has been in use since install and is a local partition on the same server FFCore is installed on (VM machine). I believe this has something to do with "paused" jobs on the server possibly.