# Troubleshooting

## TLML Syntax

Teneo Studio performs checks and validations to help developers spot and correct potential errors in the TLML Syntax, these are visible to the developer through syntax highlighting ([read more here](user-guide/match-requirements/syntax-editor?id=syntax-highlighting)) and error messages. 



#### __Teneo Studio Desktop__

The below table lists the most common errors which can occur while working on the TLML Syntax condition in the Syntax editor of Language Objects, Syntax Match Requirements, Listeners, etc. most of these are both highlighted in the TLML Syntax editor, displayed in the [Tryout](user-guide/tryout/advanced-tryout-detailed-information?id=errors-and-warning-messages) and included in [Suggestions](user-guide/optimization/improvement-suggestions).

| Error message | Example | Comment | More information |
| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Closing parenthesis directly after operator | (word&) | Indicates that the developer might have forgotten to add a word or reference to a Language Object or Entity | [Bracketed condition](reference/teneo-programming/condition-reference-manual?id=bracketed-condition) |
| Compound-operator may only be used with single words without options | `%LOB § word` `word § %LOB` `%LOB§word` | The Compound operator (\| or `§`) can only be used together with plain words (i.e. no use of Language Objects nor Entities is allowed) on both sides of the operator | [Compound operators](reference/teneo-programming/condition-reference-manual?id=compound-operator) |
| Condition option not allowed | `%LOB:1` `:e` `%LOB:E` `:L` `word:L` `word:o` `%LOB:O` | Condition options can be attached to a condition and allow to modify a certain aspect of the condition behavior | [Condition options](reference/teneo-programming/condition-reference-manual?id=condition-options) |
| Condition predicate script / variable propagation script not allowed | `word^{script}` `word:{script}` | This covers problems with attached scripts | [Variables and attached scripts](reference/teneo-programming/condition-reference-manual?id=nlu-variables-and-attached-scripts) |
| Condition terminated incorrectly | `word+` | This indicates that the developer might have forgotten to add a word, Language Object or Entity after the operator | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) |
| First operand missing | `&word` `!` `|word` | Indicates that the developer might have forgotten to add a word, Language Object or Entity between two operators or before the use of an operator | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) |
| Incomplete dynamic word condition | `#` | The syntax for the dynamic condition is incomplete | [Dynamic condition](reference/teneo-programming/condition-reference-manual?id=dynamic-condition) |
| Incomplete successor or topic condition | `@` | The syntax for the successor or topic condition is incomplete | [Topic condition](reference/teneo-programming/condition-reference-manual?id=topic-condition) |
| Invalid number of quotes | `"word` `word >> "& >> word2` | Quotation marks in TLML Syntax have to be always duplicated, so one at the beginning of the word and another at the end | [Condition syntax](reference/teneo-programming/condition-reference-manual?id=condition-syntax) |
| Missing opening brace | `script}` | Script expression have to be enclosed in curly brackets `{}` when writing script conditions | [Script condition](reference/teneo-programming/condition-reference-manual?id=script-condition) |
| Missing opening parenthesis | `word + word2) / word3` `word + word2)` | Parentheses or brackets are used to group and organize condition parts and are especially useful when writing [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) also, they are a necessary mean when using more than one type of operators in a condition to determine which parts of the condition belongs together, and for the condition to be valid there need to be both an opening bracket and a closing bracket | [Bracketed condition](reference/teneo-programming/condition-reference-manual?id=bracketed-condition) |
| Missing or Invalid option value | `word:` `word: + x` `word:x` | Condition options can be attached to a condition and allows to modify a certain aspect of the condition behavior, the condition option is added to the condition by use of `:` (colon) plus the wanted option (`:1`, `:E`, `:L`, `:O`) | [Condition options](reference/teneo-programming/condition-reference-manual?id=condition-options) |
| Name of language object / entity missing | `%` | This covers errors where a percentage sign is written but the name of the Language Object/Entity is not present | [Language Object condition](reference/teneo-programming/condition-reference-manual?id=language-object-condition) |
| Operator at invalid location | `word / / word2` `word +` `(word +)` `word |` `word | / word2` | Indicates that the developer has forgotten to add a word, Language Object or Entity between two operators or before/after the use of an operator | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) |
| Operator expected | `(word1) word2` `word1 word2` `word1 (word2)` `%LOB1 %LOB2` `%LOB %ENTITY` | TLML Syntax needs operators between words, Language Objects, Entities and other syntax elements | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) |
| Parenthesis not closed | `word + (word2` | Parentheses or brackets are used to group and organize condition parts and are especially useful when writing [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) also, they are a necessary mean when using more than one type of operators in a condition to determine which parts of the condition belongs together, and for the condition to be valid there need to be both an opening bracket and a closing bracket | [Bracketed condition](reference/teneo-programming/condition-reference-manual?id=bracketed-condition) |
| Script condition terminated incorrectly | `{script` `(word):{script` `(word)^{script` | Script expression have to be enclosed in curly brackets `{}` when writing script conditions | [Script condition](reference/teneo-programming/condition-reference-manual?id=script-condition) |
| Successor condition not supported | `word$@42` `@0123` `@"123"` | The syntax for the successor is not supported | [Condition syntax](reference/teneo-programming/condition-reference-manual?id=condition-syntax) [Topic conditions](reference/teneo-programming/condition-reference-manual?id=topic-condition) |
| Unterminated condition comment | `word == comment` | Comments inline TLML Syntax are written by the use of two equal symbols (`==`) at the beginning and at the end of the comment | [Comments](reference/teneo-programming/condition-reference-manual?id=comments) |
| Whitespace not allowed before opening brace of condition predicate / propagate script | `(word)^ {script}` | | [Variables and attached scripts](reference/teneo-programming/condition-reference-manual?id=nlu-variables-and-attached-scripts) |

#### __Teneo Studio Web__

In Teneo Studio Web, syntax errors can also be displayed through error messages in the TLML Syntax editor as displayed in the below image; hovering over the red __x__ displays a message with more information.

![Syntax error in a Syntax Match Requirement](media/troubleshooting-tlml-syntax/web-syntax-error-highlighting.jpg)

The below table lists the most common error messages which can occur while working on the TLML Syntax condition in the Syntax editor of Language Objects, Syntax Match Requirements, Listeners, etc.

| Error message | Example | Comment | More information |
| -------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Condition option ":1" not allowed in this context | `%LOB:1` | Condition options can be attached to a condition and allow to modify a certain aspect of the condition behavior | [Position option](reference/teneo-programming/condition-reference-manual?id=position-option) |
| Condition option ":E" not allowed in this context | `:e` `%LOB:E` | Condition options can be attached to a condition and allow to modify a certain aspect of the condition behavior | [Exact option](reference/teneo-programming/condition-reference-manual?id=exact-option) |
| Condition option ":L" not allowed in this context | `:L` `word:L` | Condition options can be attached to a condition and allow to modify a certain aspect of the condition behavior | [Longest Match option](reference/teneo-programming/condition-reference-manual?id=longest-match-option) |
| Condition option ":O" not allowed in this context | `word:o` `%LOB:O` | Condition options can be attached to a condition and allow to modify a certain aspect of the condition behavior | [Optional Match option](reference/teneo-programming/condition-reference-manual?id=optional-match-option) |
| Incomplete condition | `%` `%"NAME` `%$` `%$"NAME` `@` `@"NAME` `#` `#"NAME` | This error covers a range of condition errors | [Condition Syntax rules](reference/teneo-programming/condition-reference-manual?id=condition-syntax) [Language Object condition `%`](reference/teneo-programming/condition-reference-manual?id=language-object-condition) [Annotation condition `%$`](reference/teneo-programming/condition-reference-manual?id=annotation-condition) [Topic condition `@`](reference/teneo-programming/condition-reference-manual?id=topic-condition) [Dynamic condition `#`](reference/teneo-programming/condition-reference-manual?id=dynamic-condition) |
| Incomplete or unknown condition option | `word:` `word: + x` `word:x` | Condition options can be attached to a condition and allows to modify a certain aspect of the condition behavior, the condition option is added to the condition by use of `:` (colon) plus the wanted option (`:1`, `:E`, `:L`, `:O`) | [Condition options](reference/teneo-programming/condition-reference-manual?id=condition-options) See [Reserved characters](reference/teneo-programming/condition-reference-manual?id=reserved-characters) to use colon as part of the condition |
| Missing condition operand | `word / / word2` `word +` `(word +)` `!` `| word` `word |` `word | / word2` | Indicates that the developer has forgotten to add a word, Language Object or Entity between two operators or before/after the use of an operator | [Or operator `/`](reference/teneo-programming/condition-reference-manual?id=or-operator) [Followed by operator `+`](reference/teneo-programming/condition-reference-manual?id=followed-by-operator) [Not operator `!`](reference/teneo-programming/condition-reference-manual?id=not-operator) [Compound operator `|`](reference/teneo-programming/condition-reference-manual?id=compound-operator) |
| Missing condition operator | `(word1) word2` `word1 word2` `word1 (word2)` `%LOB1 %LOB2` `%LOB %ENTITY` | TLML Syntax needs operators between words, Language Objects, Entities and other syntax elements | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) |
| Mixed operators without brackets | `&word` `word + word2 / word3` `(word + word2 / word3` `~` `>>` `&=` | Brackets are used to organize the use of different types of operators within a TLML Syntax condition; this error occurs because two or more operators are used without applying brackets to specify which parts of the condition should be organized together | [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) [Bracketed condition](reference/teneo-programming/condition-reference-manual?id=bracketed-condition) |
| Predicate script not allowed in this context | `word:{script}` | Predicate scripts allow to capture and/or condition on information coming from inputs and are attached to bracketed condition parts, Language Objects, Entities or input annotation references with the `:` (colon) and embedded inside curly braces `{}` | [Predicate scripts](reference/teneo-programming/condition-reference-manual?id=predicate-scripts) |
| Propagation script not allowed in this context | `word^{script}` | Propagation scripts allow to propagate NLU Variables to the top level condition and can be attached to bracketed condition parts, Language Objects, Entities, input annotation references or directly after an attached predicate script by the use of the `^` (caret) symbol and embedded inside curly braces `{}`. | [Propagation scripts](reference/teneo-programming/condition-reference-manual?id=propagation-scripts) |
| Unclosed comments | `word == comment` | Comments inline TLML Syntax are written by the use of two equal symbols (`==`) at the beginning and at the end of the comment | [Comments](reference/teneo-programming/condition-reference-manual?id=comments) |
| Unclosed quoted word | `"word` `word >> "& >> word2` | Quotation marks in TLML Syntax have to be always duplicated, so one at the beginning of the word and another at the end | [Condition syntax](reference/teneo-programming/condition-reference-manual?id=condition-syntax) [Reserved characters](reference/teneo-programming/condition-reference-manual?id=reserved-characters) |
| Unclosed script | `{script` `(word):{script` `(word)^{script` | Script expression have to be enclosed in curly brackets `{}` when writing script conditions | [Script condition](reference/teneo-programming/condition-reference-manual?id=script-condition) [NLU Variables and attached scripts](reference/teneo-programming/condition-reference-manual?id=nlu-variables-and-attached-scripts) |
| Unmatched bracket | `word + word2) / word3` `word + (word2` `word + word2)` | Parentheses or brackets are used to group and organize condition parts and are especially useful when writing [Compound conditions](reference/teneo-programming/condition-reference-manual?id=compound-conditions) also, they are a necessary mean when using more than one type of operators in a condition to determine which parts of the condition belongs together, and for the condition to be valid there need to be both an opening bracket and a closing bracket | [Bracketed condition](reference/teneo-programming/condition-reference-manual?id=bracketed-condition) |
| Unrecognized input | `(word)^ {script}` | This error can cover, for example, whitespaces not allowed before opening braces of a predicate script | |
| Wrong operand type for compound operator | `%LOB § word` `word § %LOB` `%LOB§word` | The Compound operator (\| or `§`) can only be used together with plain words (i.e. no use of Language Objects nor Entities is allowed) on both sides of the operator | [Compound operator](reference/teneo-programming/condition-reference-manual?id=compound-operator) |

RELEASE NOTES

Platform Dependencies

Dependencies and Licenses

Prerequisites of Teneo Frontends

Teneo 7.0

Teneo 7.0.1

Teneo 7.0.2

Teneo 7.0.3

Technology and deployment

Teneo Studio

KNOWLEDGE BASE

Annotations

Annotations in Engine

Annotations in Studio

Bulk Import formats

Format Entities

Format Language Objects

Format Question and Answer pairs

General about format

Condition writing

Condition coding

TLML syntax summary

Limit unused words to

Draft TLML Syntax

Sentence test order and stop testing

General

FAQs

Input Processors

Custom configuration

Log data

Data model

Metadata

Machine learning

Class Manager

Class Performance

Publish

Solution publish

Resources

Lexical resources

Lexical resources for log data analysis

Teneo naming conventions

Scripts

Global Scripted Context

NLU Variables and Propagation scripts

Predicate scripts

Using scripts

Variables and Listeners

Solution

Localization setup

Multiple Flow Triggers

Skip Conditions

Predefining template solutions

Prompt Triggers

Relative ordering

Resume Prompts

Safetynet and default output

Sub-flows

What does a Flow consist of

Teneo Engine

Environment recognition

Output parameters

Processing path

Script and Listener events in the matching process

Stack of active flows

The answering process

REFERENCE

API reference doc

Teneo Inquire client

Interfacing with API JSPs

Web Socket API

NLP Capabilities

Chinese IP Chain

Japanese IP Chain

Korean IP Chain

Date and Time

Named Entity Recognizer

POS Tagger

Standard IP Chain

Turkish IP Chain

Conversational Modules

Date & Time

Deprecated objects

Pre-built Entities

Flow lists

Named Entity ANNOT objects

POS/Morphology ANNOT objects

Dialogue Resources

Lexical Resources

Offensive Language Detection

Sentiment & Intensity Analysis

Teneo Linguistic Modelling Language (TLML)

Teneo Query Language (TQL)

Auto-test

Auto-test results panel

Automated testing

Class management

Class manager window

Working with Classes and training data

Entity

Entity Basics

Entity Window

Entries Editor

Variables

Flow

Bot Output

Data Actions

Flow Basics

Flow Link

Flow Listener

Nodes and elements

Flow Variable

Flow window

Integration

Match Requirements

Prompt

Script

Sub-flow

Transition

User Intent

Globals

Emotions

Global Listeners

Global scripts

Global Variables

Metadata definitions

Global Context

Import Export

Bulk import

Export/Import of lexical resource

Importing and exporting

Merging solutions

Language Object

Language Object Basics

Language Object Window

Listeners and Variables

Creating a Listener

Creating Flow and Global Variables

Optimization

Class performance

Classifier

Improvement suggestions

Querying log data

Ordering

Ordering groups

Ordering suggestions

Trigger ordering window

Working with trigger relations

Publish environments

Publish a solution

Assign a lexical resource

Integrate external services

Resource Files

Document Basics

Version Control

Keyboard Shortcuts

Lexical Resource Information

Properties Lists

Localization Structure

Updates From Master

Recycle Bin

Search

Solution Properties

Solution Window

Syntax Editor

Referenced Documents

TLML Syntax

Teneo Log Data Manager

Augmenters

Teneo Manager

Get Started

Import/Export

Lexical

Solution Basics

Spellcheck

User Permissions

Login

Tryout

Advanced Tryout

Detailed information

TENEO 7.0.3

Table of Contents

Troubleshooting

TLML Syntax