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

No functional DataFlow nodes found exceptions



The No functional DataFlow nodes found exceptions occur in the Pega Diagnostic Cloud.


Error Messages

Observing Exception-1281 more frequently in PDC. Exception Details java.lang.IllegalStateException: No functional DataFlow nodes found. at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.activateRun( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.access$200( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl$4$ at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl$4$ at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.executeOnNamedThread( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.access$300( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl$ at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl$ at com.pega.dsm.dnode.util.PrpcRunnable.execute( at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper$ at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock( at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContextInternal( at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContext( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.activate( at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceProxy.activate( at com.pega.dsm.dnode.api.dataflow.operation.DataFlowStartOperation$2.emit( at$SafeDataSubscriber.subscribe( at at com.pegarules.generated.activity.ra_action_reloadnba_54b0080dd1b0bd43626957ab559f8771.step5_circum0( at com.pegarules.generated.activity.ra_action_reloadnba_54b0080dd1b0bd43626957ab559f8771.perform( at


Steps to Reproduce

  1. Access the Pega Diagnostic Cloud  (PDC) for the Production environment 
  2. Launch the Improvement plan 
  3. Check for No Functional Data Nodes and unable to open an instance, DF-1039. The Component Mismatch errors occur


Root Cause

An issue in the custom application code or rules. The user environment does not configure when the DataFlow services and usePreloadedNBA (Next Best Action) Dynamic System Setting (DSS) is True. If the usePreloadedNBA DSS is True then the system invokes the ReloadNBA Declare Trigger. The ReloadNBA Declare Trigger internally invokes the ReloadNBA activity which inturn invokes the Data Flows. The error occurs in the Pega Rules log as the environment does not have Data Flow Services.



Perform the following local-change:
Set the usePreloadedNBA DSS value to False which is required when the application uses the Artificial Intelligence (AI) features.


Suggest Edit

Published 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