Campaign run creates Data Flow dynamically with TTL of 30 days
SummaryWhen the user runs a Campaign in Pega Marketing Outbound solution, MKTG Engine internally dynamically creates a Data flow calling a Strategy with TTL Setting of 30 days, writing all data to Dnodes.
When the user tries to input the value less than 60 in DSS setting ADMTimeoutForDelayedLearning
Steps to ReproduceSet DSS setting ADMTimeoutForDelayedLearning less than 60 and run the campaign.
Root CauseThe Data Flow creation is failing due to the restriction of minimum “1 minute” set in Step 17 of the activity “AutoGenerateDF”
ResolutionFollowing minimum value for the two DSS settings in the following screenshots:
2. ADMTimeoutForDelayedLearning : 1 since there is no validation check for it. 1 is the minimum value though as 0 will consider all the past data.
- ADMTimeoutForDelayedLearning : 60 since there is validation check in AutoGenerateDF activity to be minimum of 1 minute.
The system settings are global for all outbound channels, so tuning down the setting for this case will mean that if user enables email or SMS in the future, there will be no learning there either. It is highly recommended that you scope out space to store this data. In the future this data may be used for more than learning so it is highly discouraged looking for ways to eliminate it. Since, the use case may need this requirement please note the least recommended value for both the DSS settings is 300.
Published October 15, 2016 - Updated October 17, 2016