Support Article

Improper parallel/asynchronous processing of service call



A flow has been configured with a spin off subflow so a Connect SOAP integration can be executed in the background while the user continues to process the case.

The subflow is executing but not in parallel to the main flow as desired.


Error Messages

Not Applicable

Steps to Reproduce

  1. Create a parent flow.
  2. Add a spin off subflow to the parent flow.
  3. Add an assignment task after the subflow. 

Root Cause

User is trying to harness parallel processing concept of a spin off flow.

The user could work on the parent and child tasks simultaneously as the spin off flow virtually provides parallelism but this is not a true asynchronous process where the user is expecting a separate child requestor session. It is simply analogous to the concept like single process multi-tasking feature.  



Perform the following local-change:

Pega provides “Run in parallel” or “Queue” features while using the Connect-SOAP method in an activity.

These features create separate child requestors and re-sync after execution of the service call.

​As a best practice, using the “Run in parallel” or “Queue” features provides a true sense of asynchronous processing. 


Published November 29, 2016 - Updated December 9, 2016

Have a question? Get answers now.

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