2020.1

LPD Input task will run trigger-based if they are set to run As soon as possible
with a Polling interval of 0. This reduces CPU usage.
Note
In order to wake up a trigger-based process that starts with the HTTP Server Input
task the server issues a signal to all trigger-based processes, not just those that
start with an HTTP Server Input task. This means that some processes may get
woken up when they do not need to. This issue only occurs in version 2020.1 and
will be fixed in version 2020.2.
l
Day(s) to keep backup: Indicate the number of days to keep backups of jobs processed
by input tasks. Note that backups will only be kept for those input tasks that have the
Keep backup file option selected and that they are required to resubmit input files.
l
Polling interval: Enter the frequency (in seconds) at which the process should verify if
there are new jobs to process. The polling interval also applies to scheduled tasks that
only run on certain times. For example, if your process polls every 30 seconds on a task
that's only scheduled to run one hour per week, it will capture the input 120 times during
that period.
Note
The polling interval is ignored when multiple files are present in the input and will
be used only when there are no longer any files to process.
l
Month: Select the month of the year when the process should be run or select All months
to have the process run all year long. This option is disabled when "As soon as possible"
is checked.
l
Week of month / by date: Select the desired option for the time grid. Note that any
selection you make in this box will be interpreted based on the selection made in the
Month box. If you chose All months in the Month box and Last in the Week of month / by
date box, then the process will run on the last week of every month. If you chose January
in the Month box and First in the Week of month / by date box, then the process will run
Page 132