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

Goal seek error appears to relate to 100% CPU utilization

SA-31186

Summary



A goal seek error appears to relate to 100% CPU utilization. The CPU spikes only last a moment or so and then appear to go away. 


Error Messages


goal seek requires missing input property .pxResults(1).pxCreateDateTime on page D_Interaction_paxxxxxxxxx; details: (unknown)


Steps to Reproduce



Unknown


Root Cause



Setting logging level to DEBUG for the class ChainingEngineUtilImpl reveals that the Rule-Declare-Expression (RDE) which was firing was a custom version of LastInteractionDateTime, as shown by this log entry:

Executing chaining activity: {pyClassName=AAA-FW-MRMCPIFW-Work, pxObjClass=Rule-Declare-Expressions, pyTargetProperty=.LastInteractionDateTime

The RDE itself was looking at a parameterized data page as follows:
 
Class: AAA-FW-MRMCPIFW-Work
Declare Expression : LastInteractionDateTime = D_InteractionHistory[Type:"CONTACT",ID:pyWorkPage.ContactId].pxResults(1).pxCreateDateTime

The problem occurred because there was no check in the When condition for the RDE to verify that pyWorkPage.ContactId existed.  

​When the error occurred, it did not exist. Therefore the RDE had no choice but to operate on the step page, which was D_Interaction_paxxxxxx; and there were no pxResults(1) on the page.

Resolution




Perform the following local-change:

Add a WHEN condition to the RDE to confirm the existence of pyWorkPage.ContactID before executing.

 
Suggest Edit

Published December 14, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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