On Completion
Configure post-task steps that run after the main operation completes. Available in all four task types.
Overview
On Completion is the final stage in every task. It allows one or more post-task steps to be configured, each running automatically after the main operation (Backup, Monitoring, or Clean-Up) completes — or, for Run Actions tasks, as the only steps.
Multiple On Completion steps can be added to a single task. Each step runs independently with its own condition. The available action types are listed under the Actions heading on the Task Properties section page.
Target adjustment is available as an action type in the On Completion step only.
Conditions
Each On Completion step has a condition that determines when it runs. Conditions are selectable only when an action is part of the On Completion step — in all other steps (Activation, Schedule, Backup) the condition is fixed at Always and cannot be changed.
- Always
- The step runs every time the task reaches it, regardless of outcome.
- All previous steps successful
- The step runs only if all preceding steps completed without errors within this execution of the task. If the task produced an error on one run but ran cleanly on the next, the action does not run on the error run but does run on the clean run.
- Any previous step produced an error
-
The step runs only if one or more preceding steps encountered an error.
This condition requires the task's Action on error setting (in Configuration → Error Handling) to be Ignore the error and continue task execution. If the task is configured to stop or deactivate on error, this condition will never trigger. It is recommended to place steps using this condition at the very end of the task to catch any errors that occurred during the run.
- No files were processed
- The step runs only if no files were transferred at any previous stage — for example because the source was empty, no files matched the configured filters, or an error prevented any transfer.