Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Subflow from spin-off not running in parallel

SA-20598

Summary



A flow with a Split join that has subflows must run in parallel. Instead it has subflows that run run in serial, that is one after the other.

Error Messages



Not Applicable

Steps to Reproduce

  1. Create a flow with a Split join shape, where each subflow calls a Connect-SOAP.
  2. Run the flow.


Root Cause



An issue in the custom application code or rules:

According to Pega 7 help given in the link below, Split join supports parallel processing of work items at the business process level.
https://pdn.pega.com/sites/default/files/help_v717/procomhelpmain.htm#definitions/s/splitjoinshape.htm#kanchor7862

It does not help SOAP calls, utilities, or others automatic steps.

Resolution



Select the Run in parallel check box of the Connect-SOAP step in the activity executed by the integration shape.
Use Connect-Wait method after the four Connect-SOAP calls to join the current session with the parallel connector requests.
As a best practice with Pega 7, use data pages to asynchronously load data using SOAP connectors. Navigate to the link given below.
https://pdn.pega.com/use-activity-methods-procedurally-and-asynchronously-load-data

Published March 12, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us