Optimization
Datasets
Use this troubleshooting information when creating and using datasets.
UNABLE TO LOAD DATA from the Data Lake
Solution: Navigate to the Compass user interface in Data Lake and validate that the query returns data as expected. See the Compass troubleshooting guide for additional information.
Warning related to MALFORMED ROWS when uploading file
Cause: This could mean that the data type selected for a field does not conform on some rows or a row has an incorrect number of columns.
Solution: Validate the separated file before upload.
The DATE / TIMESTAMP DATATYPES from the dataset file are not recognized correctly in the metadata section
Solution: When uploading a dataset from file, specify a Date & Timestamp format of the respective dataset in the Details page.
Groups
Use this troubleshooting information when creating and using groups.
UNABLE TO LOAD/RELOAD DATA from the Data Lake
Cause: This could mean that the datasets in Data Lake might have got renamed/removed.
Solution: Validate the datasets in Data Lake and try reloading the datasets if not present. If renamed, then try to replace the group with the new renamed datasets and update the model accordingly. If a group is used in multiple quest model then make sure all those quest models are updated manually.
Quests
Use this troubleshooting information when creating and using quests.
The quest has a FAILED status
Solution: Identify the failing activity and check the error log. The error log provides some information to help identify the issue.
The dataset contains MISSING VALUES
Cause: Solver might take null values and produce results that may not be optimal.
Solution: Check the dataset and handle the missing values by applying the Handle Missing Data activity before building the model.
The SCRIPTING activity fails
Solution: Confirm that the output variable is defined in the code as an output of the activity.
The error log indicates that a TIMEOUT has occurred on the quest
Solution: Stopping and restarting the quest may resolve the issue.
WHICH Solver to use
Solution: See the Solver Quick Reference in the main menu.
There is a user-defined SCRIPT or SQL activity present and running
Cause: The user has the flexibility to define a script or their own SQL which could result in long running activities.
The DATA volume is LARGE
Cause: Pre-processing on large datasets can take time.
Endpoints
Use this troubleshooting information when creating and using endpoints.
UNABLE TO DEPLOY ENDPOINT - button is disabled
Cause: The production quest must run with a status value of Finished.
Solution: The production quest runs happen automatically and the status shall be Finished for the endpoint button to be enabled.
ENDPOINT TESTING RETURNS AN ERROR
Solution:
- Validate that the endpoint has a status value of Active.
- Validate that the request payload is valid.
- Validate that the request data types correspond to the endpoint schema.
- If testing with .csv file input:
- Make sure the .csv file does not contain a header row.
- Validate that the request payload variables come in the same sequence as in the endpoint schema.
- If testing with JSON input, make sure there are no null values in the JSON.
INVOKING the endpoint for Optimal Solution through ION API FAILS
Solution: Validate that the sequence of input values conforms to the schema definition.
Endpoint creation failed for fast-track deployment workflow
Cause: Use of the same custom algorithm in different quests.
Solution: Always use a new custom algorithm when using it in quests.