Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Yashvant Nagendra (Yashvant N)
Senior Consultant
Senior Consultant
Senior Consultant
CH
Yashvant N Member since 2015 7 posts
Senior Consultant
Posted: Dec 4, 2018
Last activity: Sep 26, 2019
Posted: 4 Dec 2018 11:51 EST
Last activity: 26 Sep 2019 10:51 EDT
Closed

Error in the Data flow "DF_ProcessResponse" while storing Actuals

Summary:

After changing the Customer Spine from "PegaMKT-Data-Customer", in Pega Marketing 7.31, the campaign execution is getting failed.

All the steps present in the Installation guide was followed while configuring the Customer spine.

Analysis:

1) After configuring Multichannel campaign, seed list is performed. This test will be successful.

2) But when this Campaign is scheduled to run then it fails.

Error Message:

Primary error message in Batch Processing Data flow landing page is:
"The run failed, because it exceeds the maximum number of failed record, which is currently set to 0"

Show More

Summary:

After changing the Customer Spine from "PegaMKT-Data-Customer", in Pega Marketing 7.31, the campaign execution is getting failed.

All the steps present in the Installation guide was followed while configuring the Customer spine.

Analysis:

1) After configuring Multichannel campaign, seed list is performed. This test will be successful.

2) But when this Campaign is scheduled to run then it fails.

Error Message:

Primary error message in Batch Processing Data flow landing page is:
"The run failed, because it exceeds the maximum number of failed record, which is currently set to 0"

Main error message from Failed records in Batch Processing Data flow landing page

"com.pega.dsm.dnode.api.dataflow.StageException: Exception in stage: Actuals at com.pega.dsm.dnode.api.dataflow.StageException.create(StageException.java:37) at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onCompleted(DataFlowStage.java:385) at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$QueueBasedDataFlowExecutor$5.process(DataFlowExecutor.java:325) at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$QueueBasedDataFlowExecutor.runEventLoop(DataFlowExecutor.java:194) at com.pega.dsm.dnode.api.dataflow.DataFlow$1.emit(DataFlow.java:284) at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:57) at com.pega.dsm.dnode.impl.dataflow.task.strategy.ExecutionStrategy.executeDataFlow(ExecutionStrategy.java:90) at com.pega.dsm.dnode.impl.dataflow.task.strategy.SinglePartitionExecution.executePartitions(SinglePartitionExecution.java:56) at com.pega.dsm.dnode.impl.dataflow.task.ExecutePartitionsTask.execute(ExecutePartitionsTask.java:11) at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$ExecutePartitionsRunnable$1.run(PickupRunTask.java:148) at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$ExecutePartitionsRunnable$1.run(PickupRunTask.java:145) at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:52) at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContextInternal(ServiceHelper.java:212) at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContext(ServiceHelper.java:87) at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$ExecutePartitionsRunnable.run(PickupRunTask.java:145) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:108) at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:41) at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:44) at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:41) at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:52) at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:109) Caused by: java.lang.NullPointerException at com.pegarules.generated.pxGetCollectionConfigurationFromCa_071031_VzZYnZEJ1tdpLRaymHUsWg.pxGetCollectionConfigurationFromCache07_10_31(pxGetCollectionConfigurationFromCa_071031_VzZYnZEJ1tdpLRaymHUsWg.java:121) at com.pegarules.generated.pxGetCollectionConfigurationFromCa_071031_VzZYnZEJ1tdpLRaymHUsWg.invoke(pxGetCollectionConfigurationFromCa_071031_VzZYnZEJ1tdpLRaymHUsWg.java:96) at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:222) at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:119) at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:9201) at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflectionWithException(LibrarySupport.java:275) at com.pegarules.generated.pxInsertRecordsFromPages_071033_KOU023XMs_v3_xgnS5Bl_A.pxInsertRecordsFromPages07_10_33(pxInsertRecordsFromPages_071033_KOU023XMs_v3_xgnS5Bl_A.java:198) at com.pegarules.generated.pxInsertRecordsFromPages_071033_KOU023XMs_v3_xgnS5Bl_A.invoke(pxInsertRecordsFromPages_071033_KOU023XMs_v3_xgnS5Bl_A.java:95) at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:222) at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:119) at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:9201) at com.pega.pegarules.priv.generator.LibrarySupport.resolveAndInvokeFunctionViaReflectionWithException(LibrarySupport.java:275) at com.pegarules.generated.dataset.ra_action_actuals_04d6ae038c229fb0310373e5cdb3e87a$2$1.emit(ra_action_actuals_04d6ae038c229fb0310373e5cdb3e87a.java:177) 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.pega.dsm.dnode.impl.dataflow.SaveStageProcessor.onNext(SaveStageProcessor.java:107) at com.pega.dsm.dnode.api.dataflow.DataFlowStageBatchProcessor.commitBatchInternal(DataFlowStageBatchProcessor.java:120) at com.pega.dsm.dnode.api.dataflow.DataFlowStageBatchProcessor.commitBatch(DataFlowStageBatchProcessor.java:104) at com.pega.dsm.dnode.api.dataflow.DataFlowStageBatchProcessor.onCompleted(DataFlowStageBatchProcessor.java:90) at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onCompleted(DataFlowStage.java:381) ... 23 more"

Step to Reproduce:

1) Create new customer spine and modify in application settings
2) Create an email or SMS multichannel campaign with single proposition.
3) Optional: Perform seedlist test in campaign level, which will work.
4) Run the campaign
5) Check the data flow landing page
6) Failed Data flow along with Campaign id (P-XX) will be listed.
7) Try to restart the data flow and it will fail in DF_ProcessResponse at step where "Actuals" is getting updated.

Option Tried

1) Reconfigured the DNode and made sure Node are Normal/online.
2) All campaign-related Agents are running

Please let me know if there any solution for fixing the "Actuals" VBD.


Show Less
To see attachments, please log in.
Pega Marketing
Pega Platform
Decision Management

Posted: 7 years ago
Posted: 4 Dec 2018 12:39 EST
Raghukiran Shankhawaram (RaghuShankhawaram)
PEGA
Director, Software Engineering, 1:1 Customer Engagement
Pegasystems Inc.
IN

Hi,

Are the DDS and Real-Time Data Grid Node showing as Normal status?

Did we look at the logs to see what was the real reason of the Data flow failures? If not then I suggest you look at the logs as it will provide more details. 

Also on the data flow work item, Please click on the number under the Failed column and then click on View Details in the popup that gets launched to see the real exception.

To see attachments, please log in.
Posted: 7 years ago
Posted: 4 Dec 2018 14:46 EST
Yashvant Nagendra (Yashvant N)
Senior Consultant
Senior Consultant
Senior Consultant
CH

Thanks, Raghu for the reply.

Yes, the DDS and Real-time grid are showing Normal.

Checked the Pega logs and in most places, it just giving the keyword "Exception" without any additional detail.

The "Main error message from Failed records" is mentioned in Error message section.

To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Dec 2018 8:26 EST
Raghukiran Shankhawaram (RaghuShankhawaram)
PEGA
Director, Software Engineering, 1:1 Customer Engagement
Pegasystems Inc.
IN

If this is a persistent and recurring issue then I  would suggest you reach out to Customer Support and they can review and engage a SME to help you out.

To see attachments, please log in.
Posted: 7 years ago
Posted: 14 Jan 2019 8:34 EST
Shailendra Mishra (Shailendra Mishra)
Tata Consultancy Services
Senior Pega Developer
Tata Consultancy Services
IN

Hi Yashvant,

Have you got any resolution for this issue, I am also facing same issue. 

Thanks,

Shailendra Mishra 

To see attachments, please log in.
Posted: 6 years ago
Posted: 26 Sep 2019 10:51 EDT
Lochana Durgada Vijayakumar (Lochan_DV)
PEGA
Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Hi @MdKousik,

This post hasn't been updated since a few months now. In such cases we recommend that you create a new post for your query along with steps to replicate and any supporting screenshots/configurations/logs.

Thank you.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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