These variables are set by the Collect Node when it releases jobs. Collect will hold jobs until one of the defined release conditions are met. You may release jobs, for example, when you have collected 3000 impressions or after holding the job for 180 minutes.
Those job characteristics are meant you let you choose an execution path in the workflow based on why Collect released the jobs.
I've now upgraded and we'll see if that helps. I'll get back on it.
One way of solving this is with the collect node, but unfort I dont have that licensed yet. Now I found in the Route node something that is called "Release reason - Time of Day" and "Release reason - Time Held". I cant figure out how they are suppose to work, where do I type in the condition, ie Time Held = 120 sec ?
We do not have a hot folder polling settings since FFCore does not poll hot folders. As I understand it, FFCore subscribes to file system events.
Please upgrade to the latest version. If you still see this problem escalate to the hotline so development can take a look.
I have a Hotfolder setup which only moves PDFs to another printers hotfolder on the network.
But for every PDF I get two identical jobs in FFCores list of jobs, instead of just one.
My first idea is that this is a common file-is-still-locked-by-copying problem.
Is there settings to tell FFCore how often to check the Hotfolder?
Is there settings to tell FFCore to "wait for file = 5 seconds" ?
Meanwhile I will upgrade from 184.108.40.206 to 220.127.116.11.
Solved! Go to Solution.