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

ConcurrentModificationException on SpinOff SubFlows



User, in his main flow, has a subflow which is of type SpinOff.

After update to Pega 7.2.2 from Pega 7.1.9 user discovered that java.util.ConcurrentModificationException when starting new cases.

When the user deactivate the spin off checkbox, then it works normally. Also, when tracing the process runs without exception.

Error Messages

ERROR - Problem flow abort due to currentFlow null
at java.util.HashMap$HashIterator.nextEntry(
at java.util.HashMap$

Steps to Reproduce

1. Create a Flow with a subflow SpinOFF checked.
2. Create an activity that call
addWorkObjectParty() to modify the pyWorkParty.

3. Create a Declare trigger that watches pyWorkParty.Find the below screenshot.

SortedParties Activity is as below:

Root Cause

An issue in the custom application code or rules.

In the custom Trigger activity (SortParties), user is just looping through the pyWorkParty objects and adding them to SortedParties list.

Because the Trigger activity is supposed to be called on every modification to pyWorkParty(), this SortedParies list grows for ever and no where the SortedParties list are cleared.


Perform the following local-change:

User is suggested to clear the SortedParties list in the Trigger activity.

For Example: Add a step to use Property-Remove of Primary.SortedParties before Property-Ref.

Published April 11, 2017 - 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