Adaptive Decision Manager does not capture responses for adaptive models
in the Adaptive Models Management landing page, but the number of updated models is zero.
There are two possible explanations for this issue:
- A mismatch between the context keys, for example:
A decision is made for a specific Issue/Group/Name/Channel combination with the following values: Sales/Phones/Samsung Galaxy S/Call Centre.
Prior to Pega 7.3, empty context values were allowed, which could cause this issue. You can check the values that are used when the model was created on the Adaptive Models Management landing page
When the response is captured, if the value for Channel is then set to CallCentre or Call Center or any other different spelling, there is a mismatch between the context values of decision and response. Consequently, the response cannot be assigned to a model and is not captured. You can check the values that are used when the response is captured by clicking Show last responses on the Adaptive Models Management landing page.
- A mismatch between the outcome values
The outcome values that were set in the Adaptive Model rule instance are different from the values that were received in the response. For example, the positive outcome of the Adaptive Model rule is set to Accept, but the value of pyOutcome that is passed at response capture is Acceptedand the model cannot learn from such a response.
Solution - Problem with the context keys
Make sure that the context keys of an adaptive model at the response time are the same when the response is captured. You might need to ask a strategy designer to review the strategy that you use.
Solution - Problem with the outcome values
Add the response that you get in the Outcome tab of the Adaptive Model rule instance. For more information, see Defining outcome values in an adaptive model.
Published September 5, 2016 — Updated May 18, 2018