Task transfer exceptions let you control what a Traditional or Advanced task does when it runs after a previous failure.
When a task fails after transferring some, but not all, of its files, an entry is created in the task's state file, listing the files that have been completely or partially processed. These files are the task transfer exceptions. The next time that the task runs, MOVEit Automation does not perform duplicate processing on the files that were processed successfully during the previous processing. This prevents duplicate posting of files. When a task succeeds, any task failure history is removed from the state file.
You can remove entries that were processed successfully by a previous run of a task, so that the next time the task runs, the files that you have removed from the exceptions list will be processed again.
The Edit Transfer Exceptions dialog box opens. If a previous run of the task was unsuccessful, the files that were successfully transferred appear in the list. These files are not transferred during subsequent task runs.
Files that you remove are transferred during the next run of the task.
Files that remain in the list are not transferred again during the next run of the task.
Example 1
A task has two destinations. During a task run, it downloads files A and B and sends them to Destination 1, but cannot send them to Destination 2. MOVEit Automation marks both files as having been sent to Destination 1 but not Destination 2. The next time that the task runs, it downloads the files again, but sends them only to Destination 2.
Example 2
A task has one destination that is an unreliable FTP server. On a task run, it downloads files A and B and sends A successfully to the FTP server, but the FTP server crashes while B is being sent. MOVEit Automation marks file A completely processed. Then the next time the task runs, file A is not downloaded. File B is downloaded and sent to its destination.