The event is processed in Pega and we get the following response:
<ns1:EventPayloadResponse xmlns:ns1="EventPayload"> <Status>OK</Status> <Message>MyTestEvent has occurred, the following programs will be executed : NBA Dataflow DFE0f1d3ead4825253d67402c5e412b85df13bf9008</Message> </ns1:EventPayloadResponse>
It seems that no action is selected by the data flow, even though we expected some of the actions to be chosen and some of the email to be sent to the customer.
Is there any way to understand why the automatically generated data flow is filtering out every action?
We had a similar issue when using recurring schedule instead of event trigger and we solved it deselecting "Outbound model maturity" in NBA designer. Is there any other settings to change?
@SilviaZ3. It isn't recommended to turn OFF "Outbound model maturity" as this could result in all customers receiving the same new (immature) action since new actions are initially weighted with a higher priority to ensure they compete against mature actions. If you want to ensure the action gets communicated based off an event, you can mark the action as Transactional which will skip running the Prediction for the action and use the StartingPropensity as the propensity used in prioritization. The Prediction is where model maturity logic gets applied.
Posted: 4 months ago
Posted: 26 Jul 2022 12:13 EDT
Silvia Zicca (SilviaZ3)