cancel
Showing results for 
Search instead for 
Did you mean: 
4 Replies
rdanough
New Member
New Member

Re: Remote Hot Folder

Thanks for this info jyri. Our IT guy is going to look into this. Hopefully this issue will be resolved soon!

Thanks again.

0 Kudos
JyriS-Xerox
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator

Re: Remote Hot Folder

From some file servers FreeFlow Core doesn't get the information of a new file in the hot folder via subscription, which is the common method of Core finding there is something to work on. As a secondary method, Core can check the folder for files, but by default this is done once every hour. If your file server doesn't support subscirption you can increase the check interval. To do that modify MantisService.exe.config in a notepad. This configuration file is in the installation directory "\Program Files\Xerox\FreeFlow Core\MantisService.exe.config".
The default setting is:
<add key="hotFolderRecoveryIntervalInSeconds" value="3600" />

Note: before modifying this file, please make a backup of it in case you need to go back to the original.

 

rdanough
New Member
New Member

Re: Remote Hot Folder

I checked this setting and it is already set as "1".

0 Kudos
DavidU54339-XRX
FreeFlow Production Workflow Moderator
FreeFlow Production Workflow Moderator

Re: Remote Hot Folder

Look at C:\Xerox\FreeFlow\Core\00000000-0000-0000-0000-000000000000\Config\HFList make sure the JobPriority for the remote folder is set to "1' (edit to 1 if necessary) . On my machine the remote hotfolders default to a priority of 50 at creation time.

0 Kudos
rdanough
New Member
New Member

Remote Hot Folder

We have a "remote" hot folder on another server. This hot folder works, however, jobs will sit in the folder for hours before being picked up and processed. The only exception to this behavior is when we go into the settings and manually change the job priority. Then, the job is picked up immediately whether we go from "normal to high" or "high to normal". Is there a setting someplace in Core that can adjust this wait time?

0 Kudos