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

Values in pyWorkPage are different with and without Tracer



The pyWorkPage data, associated with an asynchronous Data Page load, values differ when the load is traced than when the load is not traced.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create an activity to perform an asynchronous load of a Data Page and make changes to the pyWorkPage based on the Data Page.
  2. Run the activity without Tracer active.
  3. Run the activity with Tracer active.

Root Cause

An issue in the custom application code or rules. A Pool ID was not provided to the Load-DataPage or Connect-Wait methods in the activity causing the pyWorkPage processing to occur before the Data Page was fully loaded. When traced, the processing was slowed down by the Tracer to allow the Data Page enough time to load.


Perform the following local-change to provide a Pool ID to the Load-DataPage and Connect-Wait methods.

Published October 13, 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