Using Exception Handling

  1. Open the Load Plan Editor:
    • Navigate to the Steps tab of the Load Plan Editor.
  2. Select the Step:
    • In the Steps Hierarchy table, select the step for which you want to define exception behavior.
    • The Property Inspector will display the properties of the selected step.
  3. Set Parameters in Exception Handling Section:
    • In the Exception Handling section of the Property Inspector, configure the following parameters:
      • Timeout (s):
        • Enter the maximum time (in seconds) that the step is allowed to run before it is aborted.
        • When the timeout is reached, the step will be marked as error and the associated Exception step (if defined) will be executed.
        • Note: The exception step itself will not time out. If needed, set a timeout on a parent step to prevent long-running situations.
        • A zero (0) timeout means infinite timeout (no timeout limit).
      • Exception Step:
        • From the list, select the Exception step to execute if this step fails.
        • Only exception steps defined in the Exceptions tab of the Load Plan Editor will appear in this list.
        • If no exception step is selected, the default behavior will apply (i.e., no exception handling).
      • Exception Behavior:
        • Choose how the step behaves when an exception occurs:
          • Run Exception and Raise: Executes the exception step (if any) and raises the exception to the parent step, causing the parent to fail.
          • Run Exception and Ignore: Executes the exception step (if any) but ignores the failure, notifying the parent step of a successful run. If the exception step fails, the parent step will be notified of the failure.
  4. Configure Exception Handling for Parallel Steps (if applicable):
    • For Parallel steps, the following additional parameters can be set:
      • Max Error Child Count: Defines the maximum number of child steps that can fail before the parallel step itself is considered failed.
        • If the number of failed child steps exceeds this value, the parallel step is marked as failed.
        • Based on the Restart Type configuration, the behavior differs:
          • Restart from failed children: The Load Plan waits for all child sessions (both running and waiting to be executed) to complete before raising the error to the parent step.
          • Restart all children: The Load Plan stops all running child sessions and does not start new ones before raising the error to the parent.

 

No comments:

Post a Comment