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

¿¿¿¿¿¿¿Unable to locate Call Interaction error in PegaRules log

SA-81180

Summary



Pega Customer Service 7.21 is installed on Pega Platform 7.2.2.

Unable to locate Call Interaction error is generated multiple times in the PegaRules log.


Error Messages

Unable to locate Call Interaction with ID 73290750;java.lang.Throwable;    at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_33108d96a540e2a09897cccccbf60534.step4_circum0(ra_action_pygetinteractioninternal_33108d96a540e2a09897cccccbf60534.java:518);    at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_33108d96a540e2a09897cccccbf60534.perform(ra_action_pygetinteractioninternal_33108d96a540e2a09897cccccbf60534.java:144);    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553);    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711);    at com.pegarules.generated.activity.ra_action_getinteraction_501a944a4dbc9ea3927c5fa93ac84fec.step1_0_circum0(ra_action_getinteraction_501a944a4dbc9ea3927c5fa93ac84fec.java:190);    at com.pegarules.generated.activity.ra_action_getinteraction_501a944a4dbc9ea3927c5fa93ac84fec.perform(ra_action_getinteraction_501a944a4dbc9ea3927c5fa93ac84fec.java:76);    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553);    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711);    at com.pegarules.generated.activity.ra_action_pygetcallinteraction_97ce0efce58d6e04b5b55a80a067134a.step3_circum0(ra_action_pygetcallinteraction_97ce0efce58d6e04b5b55a80a067134a.java:379);    at com.pegarules.generated.activity.ra_action_pygetcallinteraction_97ce0efce58d6e04b5b55a80a067134a.perform(ra_action_pygetcallinteraction_97ce0efce58d6e04b5b55a80a067134a.java:113);    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553);    at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runRule(DeclarativePageDirectoryImpl.java:1051);    at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runLoadActivity(DeclarativePageDirectoryImpl.java:445);    at com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandler.loadDataPage(ReadOnlyDataPageHandler.java:294);    at com.pega.pegarules.session.internal.mgmt.base.handler.ReadOnlyDataPageHandler.findDataPage(ReadOnlyDataPageHandler.java:498);    at com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory.findDataPageInCurrentDir(AbstractPageDirectory.java:939);


Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules.
Log entry was written to the logs with the stack trace since the outbound call object was not saved.


Resolution



Apply HFix-53680.
Suggest Edit

Published August 15, 2019 - Updated December 2, 2021

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