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

**URL:** <https://forums.pega.com/t/behavioral-data-accelerator-migration-aggregation-run-not-initialized-in-higher-environment/13885>\
**Category:** General\
**Tags:** next-best-action, pega-customer-decision-hub\
**Created:** [October 28, 2026, 2:24pm UTC](https://forums.pega.com/t/behavioral-data-accelerator-migration-aggregation-run-not-initialized-in-higher-environment/13885 "2026-10-28T14:24:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AvinashB17320727](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@AvinashB17320727](https://forums.pega.com/u/AvinashB17320727)\
**Post date:** [October 28, 2026, 2:24pm UTC](https://forums.pega.com/t/behavioral-data-accelerator-migration-aggregation-run-not-initialized-in-higher-environment/13885/1 "2026-10-28T14:24:38Z")

</div>

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:

---

<div class="post-metadata">

**Author:** ![Sairohith](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/sairohith/32/23362_2.png) [@Sairohith](https://forums.pega.com/u/Sairohith)\
**Post date:** [November 12, 2026, 12:23am UTC](https://forums.pega.com/t/behavioral-data-accelerator-migration-aggregation-run-not-initialized-in-higher-environment/13885/2 "2026-11-12T00:23:56Z")

</div>

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.
