Behavioral Data Accelerator migration: aggregation run not initialized in higher environment

Hi Team,

We are migrating a working Behavioral Data Accelerator implementation from Development to a higher environment where application rulesets are locked.

In Development, the complete flow works:

Behavioral Data REST service

→ Stream clickstream

→ ProcessClickstreamData

→ FSClickstream Summary

→ Customer profile

However, after migration, the target environment does not have a working pre-aggregation run.

What we observed

The target environment contained the Data-Admin-DataFlowScheduler-Aggregation instance, but its pyDataSets list was empty.

  1. We imported the Development scheduler instance. It now lists FSClickstream as active, but retains the source environment’s pzRTDataFlowHandle.

  2. The referenced run did not exist in the target environment, and the pre-aggregation run link was disabled.

  3. We subsequently transferred the referenced run work instance. Opening it fails with:

    java.lang.IllegalStateException:

    **Loaded a work object [Agg_DF_…] while no run config was present.
    **
    We recognize that transferring the work instance alone did not establish the required runtime configuration. We have paused further runtime changes pending guidance.

    Questions

    • Is there a documented migration procedure specifically for the Behavioral Data Accelerator and its generated Summary artifacts?
    • Which rules and data instances must be included in the deployment package?
    • Should Data-Admin-DataFlowScheduler-Aggregation be migrated or generated locally?
    • How should the target environment initialize its own pre-aggregation run without unlocking application rulesets?
    • What is the supported recovery procedure for the copied run work instance and scheduler reference?
    • Has anyone completed a similar migration and can share the deployment and post-deployment steps?

    We have reviewed the component installation instructions and CPD/Context Dictionary migration guidance, but have not identified the aggregation-runtime initialization steps for this scenario.

    Environment details

    • Pega Platform version/patch: 25.13
    • Customer Decision Hub version/patch: 25.1.3
    • Behavioral Data Accelerator version: 2.1
    • Transfer method for the run instance: Product Import

    A support case is also being raised. Any release-specific documentation or implementation experience would be appreciated.

    Thanks!

The error shows that the copied run is missing its runtime configuration in the target environment.
Use your existing Pega Support case to obtain the cleanup and initialization procedure for version 25.1.3.
First, verify that FSClickstream, its generated classes and properties, the source data flow, and customer-profile association were deployed.
Deploy any missing rules from Development through the normal deployment process, keeping the target rulesets locked.
Have Support confirm how to repair the copied Agg_DF work instance and the stale pzRTDataFlowHandle reference.
Then apply their procedure to initialize a valid aggregation run locally in the target environment.
The exact recovery steps for this release could not be verified publicly, so manually deleting records cannot be presented as a supported fix.
Finally, send a test clickstream event and confirm that the FSClickstream summary and customer profile update correctly.