Skip to main content

Table of Contents

Adaptive Decision Manager does not capture responses for adaptive models


Only available versions of this content are shown in the dropdown

When you click Show last responses on the Model Management landing page, the number of updated models is zero.

In addition to the following guidelines, see this Global Client Support (GCS) video, in which you will learn how to troubleshoot issues related to response capture in adaptive models: Responses not captured for Adaptive Decision Manager (ADM) model.

Cause: Context keys do not match

The model may have been created at a different hierarchy level than the level at which the values for the responses are set.

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. 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.


  1. In the header of Dev Studio, click Configure Decisioning Model Management .

  2. Click Show last responses section, and then check the values that are used when the response is captured for potential mismatches.

  3. Ensure that the context keys of an adaptive model at the response time are the same when the response is captured. Pay attention to spelling and case.

    You might need to ask a strategy designer to review the strategy that you use.

Cause: Outcome values do not match

The outcome values set in the adaptive model rule are different than the outcome values received in the response.

For example, the positive outcome of the adaptive model rule is set to Accept, but the value of the pyOutcome property that is passed at response capture is Accepted. The model cannot learn from such a response.


  1. In the header of Dev Studio, click Configure Decisioning Model Management .

  2. Check whether the outcome values in the responses received match the outcome values configured in the adaptive model rule.

  3. Add the outcome values that you get from the responses to the Outcome tab of the adaptive model rule instance.

Cause: Responses are not saved to the correct data set

The system does not save responses to the pxAdaptiveAnalytics data set.


  1. Check the data flow run and ensure that responses are saved into the pxAdaptiveAnalytics data set.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us