Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Qlik AutoML: This prediction failed to run successfully due to schema errors

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
KellyHobson
Support
Support

Qlik AutoML: This prediction failed to run successfully due to schema errors

Last Update:

Nov 16, 2022 11:16:11 AM

Updated By:

KellyHobson

Created date:

Nov 16, 2022 11:17:06 AM

Attachments

Introduction


"This prediction failed to run successfully due to schema errors"  can occur during the prediction phase if there is a mismatch in the table schema between training and prediction datasets.

In this example, we will show how a column in the prediction dataset was profiled as a categorical rather than numeric because it contained dashes '-' for empty values.

Steps

 

1. Upload test_dash_training.csv and test_dash_prediction.csv to Qlik Cloud. See attachments on the article if you would like to download.

Training dataset:

trainingsample1.png

Prediction sample:

 

predictionsample1.png

2. Create a new ML experiment and choose test_dash_training.csv, and click 'Run Experiment'

experiment.png

3. Deploy the top model

deploy.png

5. Create a new prediction and select test_dash_prediction.csv as the apply dataset

You will encounter a warning message, "Feature type does not match the required model schema."

 

feature_mismatch1.png

If you continue, you will encounter another message after clicking 'Save and predict now'.

 

mismatch2.png

6. If you click 'Save configuration', the prediction will attempt to run but will not produce prediction dataset and will display an error.

error.png

 

Resolution

 

Clean up dashes from 'chats' column in test_dash_prediction.csv. Either remove them from the prediction dataset or transform to a numeric value such as zero.

 

Environment

 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

 

Contributors
Version history
Last update:
‎2022-11-16 11:16 AM
Updated by: