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.
Steps to Reproduce
- Create an activity to perform an asynchronous load of a Data Page and make changes to the pyWorkPage based on the Data Page.
- Run the activity without Tracer active.
- Run the activity with Tracer active.
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.
ResolutionPerform 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.