Posted: 22 Dec 2017 5:54 EST Last activity: 3 Jan 2018 6:35 EST
Some PRRuntimeError in logs caused by com.pega.pegarules.pub.runtime.IndeterminateConditionalException: Trying to evaluate Rule-Access-When conditions < ACCESS WHEN NAME > when there is no page to evaluate them against
>>> Caused by: com.pega.pegarules.pub.runtime.IndeterminateConditionalException: Trying to evaluate >>> Rule-Access-When conditions <ACCESS_WHEN_NAME> when there is no page to evaluate them against
That suggests there is no requestor or thread and hence step page when one should be there. Two things to check:
1) See if this tends to occur when some user has left a Pega screen logged in for a long time, and is now attempting to click some button or menu item on the screen after it has timed out.
2) Look at the time stamp of the error in the Pega log file, and look at the last several entries before that error in the log file. Do they occur near the same second of time as that error? If so, do they provide a useful hint?
Posted: 4 years ago
Posted: 2 Jan 2018 23:09 EST
Arun Kumar Mahanty (Arun_Mahanty)
Principal Technical Solutions Engineer