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

Error thrown when stopping/pausing DataFlow Run



User is using Pega 7.3 and reported the below error when starting and then pausing the data flow run even if the data flow is not processing any records.

Error Messages

2017-08-14 13:13:37,048 [cISR:Administrators]] [ STANDARD] [ ] [ ] (ataflow.task.ExecutionDoneTask) ERROR - Post activity execution failed for run [DF-1]
com.pega.dsm.dnode.impl.dataflow.exception.ActivityExecutionException: Activity CreateOrUpdateCase failed to execute
at com.pega.dsm.dnode.impl.dataflow.service.processor.TaskActivity.runActivityLocally( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.processor.TaskActivity.runLocallyOrOnAllNodes( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.processor.TaskActivity.runActivity( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.ExecutionDoneTask.finishRun( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.ExecutionDoneTask.access$000( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.ExecutionDoneTask$2.execute( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.OperationWithLock$1.execute( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.OperationWithLock.doWithLock( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.OperationWithLock.doWithLock( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.OperationWithLock.doWithLock( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeWithLockInternal( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeWithLock( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeWithLockWithoutRetries( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.ExecutionDoneTask.forceExecution( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.ExecutionDoneTask.execute( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$1$ ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$1$ ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.PrpcRunnable.execute( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContextInternal( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContext( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.task.PickupRunTask$ ~[dnode-7.3.0.jar:?]
at$DirectExecutor.execute( ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at$CollectionFutureRunningState.handleAllCompleted( ~[guava-19.0.jar:?]
at$RunningState.processCompleted( ~[guava-19.0.jar:?]
at$RunningState.decrementCountAndMaybeComplete( ~[guava-19.0.jar:?]
at$ ~[guava-19.0.jar:?]
at$DirectExecutor.execute( ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at$TrustedFutureInterruptibleTask.runInterruptibly( ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at ~[guava-19.0.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker( ~[?:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$ ~[?:1.8.0_121]
at com.pega.dsm.dnode.util.PrpcRunnable$ ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.PrpcRunnable$ ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.util.PrpcRunnable.execute( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$ ~[dnode-7.3.0.jar:?]
Caused by: The reference "Start processing of snapshot for case with SessionID: " + .SessionID is not valid. Reason: FUAInstance-NullMyStepPage
at com.pegarules.generated.activity.ra_action_createorupdatecase_bee2abdedda5f28efbc1828ff2f2321b.step1_circum0( ~[?:?]
at com.pegarules.generated.activity.ra_action_createorupdatecase_bee2abdedda5f28efbc1828ff2f2321b.perform( ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( ~[prprivate.jar:?]
at com.pega.dsm.dnode.impl.dataflow.activity.PRPCActivities.prePostActivity( ~[dnode-7.3.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.processor.TaskActivity.runActivityLocally( ~[dnode-7.3.0.jar:?]

Steps to Reproduce

  1. Create a Kafka Data Set and then create a Data Flow to use that created Data Set.
  2. Configure Data Flow Run to process messages in real-time.
  3. While creating the Data Flow run item, configure an activity as destination for data flow processing also use the same activity as a data flow post processing activity.
  4. Start and stop the Data Flow Run and observe the error.

Root Cause

An issue in the custom application code or rules is identified as root cause. The activity used as Data Flow destination was also used as a post processing activity. The activities executed as pre or post activities don't have a step page to execute on, that's why it's null.

The post processing activity should not assume the data flow to process more than zero records.

The below explains the use of destination and pos processing activity:
  1. Destination Activity: If an activity is configured in the Data Flow rule to be the destination, it will be executed for every record that reaches this stage and the record will be the step page for the execution.
  2. Post Activity: The post activity, configured when you create a new run, will be triggered once the data flow runs gets to an end stage, be it stopped, failed or completed regardless of the number of records that were processed. When executing this activity there's no step page provided as this works as a wrap up of the whole data flow run.


Perform the following local-change steps:
  1. Create a new Data Flow Run item (not a new Data Flow rule).
  2. Ensure that the same activity is not configured as both Data Flow destination and as post processing activity for Data Flow run.

Published December 5, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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