Support Article
Exception 8207 for Inbound correspondence InteractionCMF
SA-76951
Summary
With Pega Customer Service 7.31 running on Pega 7.3.1 (Cloud Version 2.8), multiple exceptions occur despite not using the Pega-provided CustomerJourney timeline feature to input data to the CustomerJourney timeline widget. This occurs when the Capture event code is invoked in the CPMInteraction flow. Data flow InteractionCMF generates Exception 8207 in the log.
Error Messages
Exception-8207
| GenerateDateTime: | |
| RootExceptionClass: | com.pega.dsm.dnode.api.ExceptionWithInputRecord |
| RootExceptionMessage: | Could not save record: The parameter pxEventId is empty |
| TopLevelExceptionClass: | com.pega.dsm.dnode.api.dataflow.StageException |
| TopLevelExceptionMessage: | |
| ThreadName: | EMAIL-Thread-18 |
| ProblemCorrelation: | dmgxx-prod1:EXCEPTION:2adde012ca639985a6dcd48d905a7aa4 |
| Stack: |
EMAIL.ServiceKuchenDirect.Listener|from([email protected])|sub(Re: Verzoe)|Email|DMGCSEmailDefault|DMG-CS-Work-Interaction-InCorr|CreatepyStartCase|A54ELZMEKO3XX0BTGIY1GCKEJSC9TOX4D |
| Type | com.pega.dsm.dnode.api.dataflow.StageException | |
| Message | Exception in stage: Event store | |
| Stack |
at com.pega.dsm.dnode.api.dataflow.StageException.create(StageException.java:37) at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onNext(DataFlowStage.java:332) at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onNext(DataFlowStage.java:262) at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$SynchronousQueueDataFlowExecutor$2.process(DataFlowExecutor.java:582) at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$SynchronousQueueDataFlowExecutor.runEventLoop(DataFlowExecutor.java:556) at com.pega.dsm.dnode.api.dataflow.DataFlow$5.emit(DataFlow.java:523) at com.pega.dsm.dnode.impl.stream.DataObservableImpl$SafeDataSubscriber.subscribe(DataObservableImpl.java:335) at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:53) at com.pega.dsm.dnode.api.dataflow.operation.DataFlowSaveOperation$1.emit(DataFlowSaveOperation.java:30) at com.pega.dsm.dnode.impl.stream.DataObservableImpl$SafeDataSubscriber.subscribe(DataObservableImpl.java:335) at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:53) at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:99) at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:88) at com.pegarules.generated.activity.ra_action_defineeventdataflow_e65b76a1eba3052a6c3668681d1e9675.step8_circum0(ra_action_defineeventdataflow_e65b76a1eba3052a6c3668681d1e9675.java:677) at com.pegarules.generated.activity.ra_action_defineeventdataflow_e65b76a1eba3052a6c3668681d1e9675.perform(ra_action_defineeventdataflow_e65b76a1eba3052a6c3668681d1e9675.java:217) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3601) at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10849) at com.pegarules.generated.activity.ra_action_captureevent_a651cd6b5b8d246183671747d3732e95.step4_circum0(ra_action_captureevent_a651cd6b5b8d246183671747d3732e95.java:353) at com.pegarules.generated.activity.ra_action_captureevent_a651cd6b5b8d246183671747d3732e95.perform(ra_action_captureevent_a651cd6b5b8d246183671747d3732e95.java:125) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3601) at com.pegarules.generated.flow.ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.RunTaskActivity(ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.java:1963) at com.pegarules.generated.flow.ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.Task_Utility1_circum0(ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.java:1069) at com.pegarules.generated.flow.ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.perform(ra_action_captureevent_97b6afa94708126e6da00b80a0d028bf.java:605) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3601) |
Steps to Reproduce
Send an Inbound correspondence.
Root Cause
The pxEventID is empty when pzInsKey is null.
In some scenarios, pzInskey is not present on the primary page. This causes the EventId to be null. To avoid this, EventId should be set from pyId if pzInsKey is not present in the primary page. A correction is needed in the EventDetails Data Transform for Inbound correspondence.
The log references to com.pega.dsm are misleading because the exception is generated from CPM and will never be applicable in the context of troubleshooting DSM components.
Resolution
Apply HFix-51864 for Pega Customer Service 7.31.
Published August 15, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.