Error handling during run

Delivery Manager handles errors interactively when you run task steps.

Interactive error messages only

When task steps are run, errors (if any) appear as dialog boxes on the screen. Delivery Manager typically logs on to a repository and a USoft tool and then calls a function that you can also call manually from that tool screen (by pressing a button, activating a menu option, ...). Any errors appear as they would if you had chosen to activate the function manually.

If a task step or a sequence of task steps completed without any error messages appearing, you can assume that the execution was successful.

Error logging

Delivery Manager does not have any overall error logging mechanism. Instead, for each executed task step, errors are logged (or not) as if you called the function manually.

Similarly, the Delivery Manager "Run Tasks" window does NOT register any errors raised. For each task step that you run, the "Run Tasks" window registers Done = Yes when Delivery Manager has finished running the task step, whether or not errors were raised. In other words, "Done" implies only: "this task step was executed". It does NOT imply: "this task step ran without errors".

When you press the Run All Next button and there are multiple tasks with Active = Yes and Done = No, Delivery Manager will NOT terminate execution as soon as an error is raised. Instead, it will produce interactive errors for each of the task steps. When the run is completed, there is no persistent record of the errors raised.

The Run All Next button is appropriate only for tasks that you run repeatedly and that you expect will run without errors.

If you are not in a position to predict that a task will run without errors, it is better to execute the task steps one-by-one by pressing the Run Next button repeatedly. This way, when an error appears, you know which task step has produced it is easier to correct the error.

Errors do not block processing

When you run a task step, it is possible that errors are raised during execution of that task step. These errors are thrown by the application called by the task step, in the database account or file system location specified in the task step. The error probably blocks execution of whatever the application was trying to do. But Delivery Manager does not itself terminate processing.

This means in particular that, when you execute multiple task steps in one go using the Run All Next button, an error raised by one task step does NOT keep Delivery Manager from executing the next task step.