Skip to main content

Common errors

A list of common errors and how to solve them.

API errors​

The following errors are returned by the API.

422 Value Error​

A 422 Value Error occurs when your API request contains fields that don't match the expected schema (e.g., extra or invalid fields).

Sample error message:

'Value error, Failed to parse V2 config: Validation error at ''data.item_tables'': Extra inputs are not permitted'

Solution:

403 Forbidden​

A 403 Forbidden error occurs when your API request does not have the correct authentication for the endpoint you are calling.

Sample error message:

A 403 error from the API with "Forbidden" in the response

Solution:

  • Ensure your API key is correct
  • Use a write API key if writing to the system (eg creating models, creating datasets)
  • Ensure the endpoint is correct – verify base URL, model or table name, path

Engine deployment errors​

This section explains some common errors that happen during engine deployment, and how to solve them.

'item_id' missing from item source​

Sample error message:

'title': 'The fetch config is invalid.', 'detail': "'item_id' missing from item source'

Solution:

  • Ensure your item_dataset contains an item_id column

'user_id' missing from item source​

Sample error message:

'title': 'The fetch config is invalid.', 'detail': "'user_id' missing from item source'

Solution:

  • Ensure your user_dataset contains a user_id column

'label' missing from item source​

Sample error message:

'title': 'The fetch config is invalid.', 'detail': "'label' missing from item source'

Solution:

  • Ensure your interaction_dataset contains item_id, user_id and label columns

Invalid datetime format​

Sample error message:

Exception: Cannot parse DateTime: Cannot parse DateTime from String: while converting column release_date from type String to type DateTime

Solution:

  • Ensure datetimes are formatted in YYYY-MM-DDZ00:00:00 format.
  • Cast any datetimes with an SQL query like: select toDateTimeOrNull(release_date) as release_date_casted from movies

Cyclic aliases​

A cyclic aliases error occurs when two columns in the input and output datasets are ambiguous. For example, you may be trying to transform a column into another column with the same alias.

Sample error message:

Exception: ClickHouse error code 174 Code: 174. DB::Exception: Cyclic aliases. (CYCLIC_ALIASES)

Solution:

  • Clear the ambiguous column name from your data config. For example, replace toDateTimeOrNull(release_date) AS release_date with toDateTimeOrNull(release_date) AS release_date_casted

Cannot parse DateTime from String​

This error occurs when the SQL parser cannot accurately cast a DateTime column from a String column.

Sample error message:

Cannot parse DateTime: Cannot parse DateTime from String

Solutions:

  • Cast columns with string dates using the toDateTimeOrNull() function. For example: select toDateTimeOrNull(created_at) as created_as_casted, * from events
  • Alternatively, use schema_override in data block to specify how Shaped should convert each column into a feature.

Invalid Huggingface model​

Sample error message:

Error: There was an error when training: sentence-transformers/modernbert is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'. If this is a private repository, make sure to pass a token having permission to this repo either by logging in with huggingface-cli login or by passing token=<your_token>

Solution: