Import errors

Mix.nlu may return errors and warnings during the import.

Unless specified otherwise (see IMPORT_ERROR_TRSX_PARSING), the import process will complete and then return the errors or warnings, if any. The difference between these two severity levels is as follows:

  • Error: A serious issue occurred. You may want to fix it and re-import the file.
  • Warning: The import process was successful, but a non-critical issue occurred.

Solving issues

Each error message below provides a recommended action for solving the issue.

You have two options for solving issues:

  1. (Recommended) Fix the error using the Mix.nlu tool. For example, if a sample was imported but not annotated, you can annotate it in the Mix.nlu tool.
  2. Fix the error in the TRSX file and re-import it again. However, this solution is not optimal since you will get warnings for all the items that have already been imported.

ANNOTATION_ERROR_ANNOTATING_WITH_CONCEPT

Unable to annotate a sample’s tokens with an entity.

The severity and action depend on the additional message provided.

Message 1: “Annotation with concept entity_name has been skipped because the entity is hidden”

Description: The sample was annotated with a hidden entity. This can happen, for example, if you try to annotate a sample with an entity that is used to define a predefined entity (for example, if you annotate a sample with entity nuance_QUANTITY_ABS, which is a sub-entity of the nuance_QUANTITY predefined entity).

Severity: Warning.

Result: The sample was added without annotation.

Action: Annotate your samples with an entity that is defined in your ontology. To get the list of entities that you can use:

  1. Log in to Mix.
  2. Select your project.
  3. Go to Mix.nlu.
  4. Use an entity that is listed in the Entities column.

Message 2: “Annotating a full sample with a freetext concept is not allowed”

Description: The complete sample was annotated with an entity of type freetext.

Severity: Error.

Result: The sample was added without annotation.

Action: Apply the freetext entity to a meaningful phrase inside the sample, not to the whole sample.

ANNOTATION_ERROR_ANNOTATING_WITH_INTENT

Unable to annotate a sample’s tokens with an intent.

The severity and action depend on the additional message provided.

Message 1: “Intent intent_name not recognized”

Description: The sample was annotated with an intent that does not exist.

Severity: Warning.

Result: The sample was added without annotation.

Action: Annotate your sample with an intent that is defined in your ontology. To get the list of intents that you can use:

  1. Log in to Mix.
  2. Select your project.
  3. Go to Mix.nlu.
  4. Use an intent that is listed in the Intents area.

Message 2: “Intent was not provided”

Description: The intent name was not specified in the sample.

Severity: Warning.

Result: The sample was added without annotation.

Action: Annotate the sample with an existing intent.

IMPORT_ERROR_TRSX_PARSING

The TRSX file you are trying to import is invalid.

The action depends on the additional message provided.

Message 1: “Failed to create data sources! Please check content of your TRSX file”

Description: There was an issue with the Sources section of the TRSX. The URI may be malformed or the data source already exists.

Severity: Error.

Result: The TRSX file was not imported.

Action: Fix the issue and try again.

Other messages: “An unexpected error occurred while loading a ‘.trsx’ file”, “Could not load XML document”, or “Unable to parse TRSX file”

Description: The file is not a correctly-formed XML document.

Severity: Error.

Result: The TRSX file was not imported.

Action: Verify the validity of your XML file using an online XML validator. Download the TRSX schema. Try the import again when your file is valid.

IMPORT_WARNING_DUPLICATE_SAMPLE_LITERAL

Description: By default, you cannot include duplicate samples in your TRSX file, unless the allowDuplicate query parameter is enabled. If this parameter is not enabled and the TRSX file includes duplicate samples (even if they have different annotations), this message is returned. An additional message similar to the following may also be provided:

  • “This sample already exists in the imported model data_source_name and cannot be modified.”
  • “The sample already exists in the imported model data_source_name in intent_name.”
  • “The sample already exists in intent_name.”
  • “The sample already exists in the imported model data_source_name but isn’t assigned to any intent.”
  • “The sample already exists in the model but isn’t assigned to any intent.”

Severity: Error.

Result: The sample was not imported.

Action: Modify the duplicate sample or enable the allowDuplicate query parameter.

IMPORT_WARNING_IGNORED_LINE

Description: A line was ignored because it is empty or commented out.

Severity: Warning.

Result: The line was ignored.

Action: No action.

NORMALIZATION_ERROR_QA_CHECKER_VALIDATION

Description: A serious error occurred when tokenizing a sample. This can occur when the annotations are not compliant with the tokens returned by the tokenizing system.

For example, consider the following sample:

pie à la mode

The tokenizer splits this utterance into the following tokens:

pie and à la mode

This means that the whole phrase à la mode must be annotated, and not only mode. If you annotate this sample as follows:

<sample intentref="order_dessert" count="1"><annotation conceptref="dessert_type">pie</annotation> à la <annotation conceptref="dessert_flavor">mode</annotation></sample>

NORMALIZATION_ERROR_QA_CHECKER_VALIDATION will be generated.

Severity: Error.

Result: The sample was added without annotation.

Action: When you encounter this error, you can try to annotate the problematic sample in the Mix.nlu user interface, as follows:

  1. Log in to Mix.
  2. Create a project with the appropriate language.
  3. Go to Mix.nlu.
  4. Select NO_INTENT.
  5. Type the problematic sample and see how you can apply annotations.

ONTOLOGY_ERROR_CREATING_CONCEPT

Unable to create an entity.

The severity and action depend on the additional message provided.

Message 1: “An exception occurred while creating concept entity_name: A concept cannot have multiple modifier properties active simultaneously”

Description: An entity cannot be of type freetext and dynamic at the same time.

Severity: Error.

Result: The entity was not added.

Action: Specify a single entity type.

Message 2: “An exception occurred while creating concept entity_name: message_details

Description: An internal error occurred while creating the entity.

Severity: Error.

Result: The entity was not added.

Action: Please contact Nuance Support.

Message 3: “An invalid data source source_name has been provided for concept entity_name

Description: The data source specified does not exist.

Severity: Error.

Result: The entity was not added.

Action: Make sure to specify a name for a source that already exists.

ONTOLOGY_ERROR_CREATING_INTENT

Unable to create an intent.

The severity and action depend on the additional message provided.

Message 1: An invalid data source source_name has been provided for intent intent_name"

Description: The data source specified does not exist.

Severity: Error.

Result: The intent was not created.

Action: Make sure to specify a name for a source that already exists.

Message 2: “An exception occurred while creating intent intent_name: message_details

Description: An internal error occurred while creating the intent.

Severity: Error.

Result: The intent was not added.

Action: Please contact Nuance Support.

ONTOLOGY_ERROR_CREATING_RELATIONSHIP

Unable to create a relationship between entities.

The severity and action depend on the additional message provided.

Message 1: An invalid data source source_name has been provided for hasA relationship between intent intent_name and concept entity_name" or “An invalid data source source_name has been provided for hasA/isA relationship between parent node parent_name and child node child_name.”

Description: The data source specified does not exist.

Severity: Error.

Result: The relationship was not created.

Action: Make sure to specify a name for a source that already exists.

Message 2: “Error while retrieving intent intent_name from the ontology in order to create a hasA relationship”

Description: The intent specified for the relationship does not exist.

Severity: Error.

Result: The relationship was not created.

Action: Specify an intent that is defined in your ontology. To get the list of intents that you can use:

  1. Log in to Mix.
  2. Select your project.
  3. Go to Mix.nlu.
  4. Use an intent that is listed in the Intents area.

Message 3: “Error while retrieving node node_name from the ontology in order to create a hasA/isA relationship” or “Error while retrieving either node_name or node_name node from the ontology in order to create a hasA/isA relationship”

Description: The entity or intent specified for the relationship does not exist.

Severity: Error.

Result: The relationship was not created.

Action: Specify an existing entity or intent.

Message 4: “Error occurred while creating hasA relationship between intent intent_name and concept entity_name” or “Error occurred while creating relationship between parent node parent_name and child node child_name

Description: An internal error occurred while creating the relationship.

Severity: Error.

Result: The relationship was not added.

Action: Please contact Nuance Support.

ONTOLOGY_ERROR_CREATING_SAMPLE

Unable to create a sample.

The severity and action depend on the additional message provided.

Message 1: “Sample sample exceeded maximum length of length_limit

Description: The sample provided is too long. A sample can contain a maximum of 400 characters.

Severity: Error.

Result: The sample was not created.

Action: Edit the sample so that it includes less than 400 characters.

Message 2: “Impossible to create sample - The literal is empty.”

Description: The sample provided is empty.

Severity: Error.

Result: The sample was not created.

Action: Specify a non-empty sample.

Message 3: An invalid data source source_name has been provided for sample sample"

Description: The data source specified does not exist.

Severity: Error.

Result: The sample was not created.

Action: Make sure to specify a name for a source that already exists.

Message 4: “Annotation on sample sample_literal with concept entity_name failed”

Description: An internal error occurred while creating the sample.

Severity: Error.

Result: The sample was not added.

Action: Please contact Nuance Support.

SEMANTIC_ERROR_ADDING_PATTERN

Unable to add a pattern (an entity’s dictionary entry ).

The severity and action depend on the additional message provided:

Message 1: “Error while retrieving concept entity_name from the ontology in order to add patterns - pattern_name.”

Description: The entity name specified could not be found.

Severity: Error.

Result: The pattern was not added since the entity could not be found.

Action: Make sure to add the patterns to an entity that is defined in your ontology. To get the list of entities that you can use:

  1. Log in to Mix.
  2. Select your project.
  3. Go to Mix.nlu.
  4. Use an entity that is listed in the Entities column.

Message 2: “Concept entity_name has some relationships and must not be associated to literals”

Description: The entity specified has relationships, so you cannot add a dictionary entry to it.

Severity: Error.

Result: The pattern was not added.

Action: Make sure to add the patterns to an entity that does not have relationships.

Message 3: “An invalid data source source_name has been provided for pattern pattern_name

Description: The data source specified does not exist.

Severity: Error.

Result: The pattern was not added.

Action: Make sure to specify a name for a source that already exists.

Message 4: “Pattern pattern_name has been dropped because it cannot be associated with concept entity_name

Description: You are trying to add a pattern to a predefined entity. This is not allowed.

Severity: Warning.

Result: The pattern was not added.

Action: No action.

Message 5: “Error while adding pattern pattern_name to concept entity_name

Description: The tokenized version of the pattern is a duplicate of an existing pattern. For example, consider the following patterns:

  • it’s
  • it ’s (notice the extra space after “it”).

While these patterns are different in their raw format, once tokenized they are identical (“it’s”). This is not allowed.

Severity: Warning.

Result: The pattern was not added.

Action: No action.

Other messages: “Internal error - no pattern was tokenized!”, “Couldn’t tokenize/normalize pattern: pattern_name

Description: An internal error occurred.

Severity: Error.

Result: The pattern was added but was not tokenized.

Action: Please contact Nuance Support.