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

ApplicationProfileSetup invoked twice on each request of thread



ApplicationProfileSetup activity is initiated twice on each request of thread. As a result, a record is deleted twice and the whole business logic works incorrectly. The issue was detected during smoke testing.

Error Messages

Not Applicable

Steps to Reproduce

  1. Update from Pega 7.1.5 to Pega 7.3.1.
  2. Open the ApplicationProfileSetup > Trace Rule.
  3. Create a case. Two requestors are displayed.

Root Cause

This feature was included in Pega 7.1.9 to provide Achievement Badges to Pega Express users. 
The batch requestor call occurred because Work-Cover-.SaveNew invoked a Queue batch activity (Queue pxTrackAction). Since an activity was executed or scheduled in the background, the ApplicationProfileSetup activity was also invoked for the batch requestor. Hence, this configuration was made to support a product feature.


As a local-change, modify the business logic such that the activity is not invoked when the requestor is of batch type.

Use the 'isBatchRequestor(tools)' function to determine if the requestor is of batch type and apply that in the Activity When condition.


Published July 23, 2018 - 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