Skip to main content
LinkedIn
Copied!

Table of Contents

Errors when running the PMML model

Version:

Only available versions of this content are shown in the dropdown

When you run a strategy that references a Predictive Model rule instance, an error that is related to the PMML file that is uploaded in the rule instance might occur.

Causes

An error occurs and a message is displayed when one of the following conditions applies:

  • Missing or invalid input values for the model
  • Data type mismatch for the model inputs
  • Missing a value for a field in the model
  • Invalid number of arguments in the model
  • Error running a custom function in the model
  • Unsupported or invalid feature in the model
  • Problem with running the predictive model

General solution

  1. For any type of error, ask a PMML developer to investigate the error message that indicates the nature of the error and fix the problem.

Cause: Missing or invalid input values for the model

Solution

  1. Check the strategy that references the predictive model and the PMML model that was uploaded in the predictive model:

    1. If values for the predictive model are missing, check the strategy for the model's inputs.

    2. Open the predictive model, and then click Actions Run .

    3. Enter values for the inputs, and click Run.

    4. Ask the PMML developer who created the model to update the model definition.

      The missing values need to be handled by the missingValueReplacement​ attribute of the MiningField element.
  2. If the error recurs, check whether the supplied values are valid.

    The correct values depend on the data type and possible values that are defined in the DataField element of the PMML model definition.
  3. If an error occurs after you provide the correct input values, there might be a problem with executing the predictive model.

    For more information, see the issue description below.

Cause: Data type mismatch for the model inputs

The type of input data must match the type that is specified in the predictive model.

Solution

  1. Modify the predictive model or the strategy that references the predictive model.

    For example, the error occurs when a strategy provides a string value for the integer property in the predictive model.

Cause: Missing a value for a field in the model

Very often this problem occurs when you specify derived fields in the PMML model that get values from the parent field, and there is a problem with the parent field.

Solution

PMML developer
  1. Investigate the derived and parent fields to provide the missing values for the model.

    An Age field derived from a DateOfBirth parent field might be missing a value if the parent field does not have a value.

Cause: Invalid number of arguments in the model

The model definition uses functions and there is a discrepancy in arguments between the function definition (the DefineFunction element) and the function call (the Apply element). The PMML model might have been incorrectly generated or modified manually.

Solution

PMML developer
  1. Investigate the function definition and its call.

Cause: Error running a custom function in the model

Solution

PMML developer
  1. Debug the custom function that is defined on the Configurations tab of the predictive model.

Cause: Unsupported or invalid feature in the model

Solution

  1. Modify the PMML model.

    For more information, see Supported models for import.

Cause: Problem with running the predictive model

Solution

  1. Check the model definition for valid input. If the problem is more complex and caused by issues with the PMML model, ask a system architect and PMML developer for help.

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