Support Article

Error not thrown in RDB-Save with RunInParallel



User has several Connect SQL's they are calling via the RDB-Save activity method with RunInParallel selected.

When one of the Connect SQLs fails, the error is not being caught either in the Jump (StepStatusFail or "On exception, jump to later step label") of the RDB-Save method or later in the Connect-Wait method.

Error Messages

Not Applicable

Steps to Reproduce

  1. Include several RDB-Save method with RunInParallel selected.
  2. Include the Connect-Wait method to wait for the Connect-SQL's to finish
  3. Enable conditions after this action in the Jump for all the above steps and include StepStatusFail in the when and have it Jump to a Error handling step and also include the same in the "On exception, jump to later step label".
  4. Simulate failure in the Connect-SQL.

Root Cause

A defect in Pegasystems’ code or rules.

Exception thrown at the child case is not getting propagated to parent when RDB-SAVE is performed with RunInParallel check enabled.


Install HFix-30996 through update manager and create a DSS named “isPropagateExceptionFromChildToParent” in "Pega-RULES" ruleset and the value should be "true".

Changes are made in ChildInvoke activity to propagate exception from the child case to parent when RDB-SAVE is performed with RunInParallel check enabled.

Published February 8, 2017 - Updated May 14, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.