task manually, or you can schedule the task to run at a specific time or when a file is ready to transfer. You can receive notifications if the task fails. You can run multiple jobs and file batches concurrently. You can also select the log level that a job creates.
On the
Runtime Options
page, under
Schedule Details
, select one of the following options:
Do not run this task on a schedule. The task does not run according to a defined schedule. You can run the task manually.
Run this task on a schedule. Select a schedule by which the task runs.
Run this task by file listener. The task runs when the file listener notifies the task of a file event. A file event occurs when files arrive to the monitored folder or the files in the monitored folder are updated or deleted.
You must create a file listener that listens to the folder where files arrive. For more information about creating a file listener, see the section "File listeners" in the
Components
help.
Under
Failure Management
, select the
Send a notification on failure
option to receive notifications if the task fails and if the task detects infected files. Enter a comma-separated list of email addresses to which to send the notifications.
If the file ingestion task detects an infected file, it copies the file from the source to the quarantine directory. The default directory path is
<agent location>/data/quarantine
.
Under
Advanced Options
, select
Allow concurrency
to run multiple file ingestion task jobs concurrently.
Running concurrent jobs might cause unexpected results if the targets include duplicate files.
Select the number of file batches to run in parallel. Default is 1.
Select the log level to determine the level of detail in the logs that the job creates. Select one of the following options:
Normal. Logs project-level information, such as the name of the user that ran the project, when the project started, any variables that were passed, and when the project stopped. It also logs any errors encountered.
Silent. Additionally logs the start and stop times of tasks.
Verbose. Additionally logs task-level details, such as the names of the files that were processed.
Debug. Additionally logs detailed debugging information, such as message responses from servers.
ASK INFAPreview
