Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Prediction Studio notification types

Updated on May 17, 2024

Prediction Studio provides various notifications that describe the status of adaptive and predictive models, as well as predictions. Use the details that are gathered in these actionable insights to monitor your models, update their configuration as necessary, and improve the predictions that support your customer-oriented strategies.

For more information about predictive performance metrics, see Metrics for measuring predictive performance.

Adaptive model notifications

NotificationDescriptionAvailable from Pega Platform version
No monitoring information for model in the last 2 days.The model instance has not had any monitoring data for the last two days.8.3
No updates to model in the last 2 days.The model instance has not been updated for the last two days. The number of responses gathered between two days ago and the time when the monitoring data was last saved has not changed.

This notification occurs only when historical monitoring data is saved.

8.3
Model performance is at its minimum of 50 AUC.The model instance area under the curve (AUC) performance equals 50.8.3
Model performance is low for adaptive model.The model instance AUC performance is between 50 and 52.8.3
Zero responses received for adaptive model.The model instance has not received any responses yet.8.3
20% less responses received within the current week compared to last week.This week’s monitoring data for the model instance contains at least 20% fewer responses compared to the previous week.8.3
Performance has dropped by 20% compared to the previous day.The model performance has decreased by more than 20% in the current monitoring data, compared to the previous day.8.3
Success rate has dropped by more than 50% compared to the previous day.The model success rate has decreased by more than 50% in the current monitoring data, compared to the previous day.8.3
No responses have been received for one of the outcomes of a binary outcome model.No responses have been collected for a positive or negative outcome, while the alternative outcome has gathered evidence of more than 1000 responses.8.4
Model has no active predictors.All predictors have a predictive performance score below the performance threshold and, as a result, are not active. The performance threshold for predictors is set to 52 AUC.

For more information, see Troubleshooting an adaptive model with no active predictors.

8.4
Model only has 1 active predictor.Only one predictor has a predictive performance score above the performance threshold. The predictors with a predictive performance score below the threshold are not active. The performance threshold for predictors is set to 52 AUC.

For more information, see Troubleshooting an adaptive model with only one active predictor.

8.4
Model performance is very high.The performance score for the adaptive model is above 95 AUC.

For more information, see Troubleshooting an adaptive model with exceedingly high performance.

8.4

Predictive model notifications

NotificationDescriptionAvailable from Pega Platform version
Model performance is low for the current week.The weekly performance of the binary outcome model is lower than 52 AUC, based on sufficient evidence of the least frequent outcome with more than 100 responses.8.3
ROC curve is under the diagonal.The ROC curve for the binary outcome model is under the diagonal, with the AUC value below 50.

This status means that the labels for the outcomes or the output score of the model should be reversed.

8.3
Performance of the model over the last month is less than 20% of the expected performance.The model monthly performance for each version is below 20% of the expected performance.

The measurement is based on the sufficient evidence of more than 100 positive and 100 negative responses for the binary outcome models, and more than 500 responses in the case of categorical and continuous outcome models.

8.3
20% less responses received within current week compared to last week.This week’s monitoring data for the model instance contains at least 20% fewer responses compared to the previous week.8.3
Performance has dropped by 20% compared to the previous day.The model performance has decreased by more than 20% in the current monitoring data, compared to the previous day.

For continuous outcome models, this notification means that the root-mean-square error (RMSE) value has increased by more than 20%, which reflects the lower performance.

8.3
Success rate has dropped by more than 50% compared to the previous day.The success rate for the binary outcome model has decreased by more than 50% in the current monitoring data, compared to the previous day.8.3

Prediction notifications

NotificationDescriptionAvailable from Pega Platform version
No lift observed over the last week.The prediction did not generate any lift in the last week. The success rate in the target group was not larger than the success rate in the model control group. The success rate in the model control group should be greater than 0.8.5
Lift has dropped by more than 10% compared to the previous week.The weekly lift decreased by more than 10% compared to the previous week.8.5
There is a model name waiting for approval to replace component name. Reference ID is M-number.A model update awaits approval. View the results of the analysis, and then approve or reject the model update. For more information, see Evaluating candidate models with MLOps.8.6
Model approval process is stopped for model name. Issue description. Reference ID is M-numberA model update process failed due to the issue described in the notification. Here are some of the issues that you might encounter:
  • A shadow model exists for the model.
  • The system failed to map all the predictors.
  • The system failed to open an instance using the given inputs.
  • The system failed to read the model source.
  • The system encountered an unknown categorical level.
Address the underlying issue and resume the model update process, or reject the candidate model.
8.6

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us