Troubleshooting
Tryout
| Error type | Error message | Implication | Resolution |
|---|---|---|---|
| Error | Solution inconsistency: Flow [Flow name] (Flow Id): Vertex [Transition name] (Id) references unknown target flow ID: [name/null] | Parsing the solution fails, the Tryout Engine doesn't start | To remove this error message, the user should edit the Flow: either delete the Flow Link node from the Flow or link to a Flow existing in the solution |
| Error | Parsing solution failed: Language component [Name] is self-referencing | Parsing the solution fails, the Tryout Engine doesn't start | To correct this error, the user should update the Language Object or Entity to not contain a reference to its own name; reload the Tryout Engine as described here |
| Error | Parsing solution failed: Language object / entity contains itself | Parsing the solution fails, the Tryout Engine doesn't start | To correct this error, the user should update the Language Object or Entity to not contain a reference to its own name; reload the Tryout Engine as described here |
| Error | Model update failed. Error in learn server: Feature extraction failed. The training data should contain at least one example that contains 4 or more characters | Parsing the solution fails, the Tryout Engine fails | Update the training data in the affected Class(es) in the Class Manager |
| Error | Model update failed. Error training model and updating Engine. Reload required. | Click the lower part of the Restart button (in the top ribbon of the Tryout window) and select Reload Engine; also see here | |
| Warning | Flow [Flow name] (Flow ID): Trigger [Trigger name] (Trigger ID): Match Requirement (MR ID): Condition syntax error: ... | TLML syntax errors cover a broad range of syntax errors which can occur in a solution, see below the table for more information. | |
| Warning | Flow [Flow name] (Flow ID): Trigger [Trigger name] (Trigger ID): Match Requirement (MR ID): Condition uses undefined Language Object / Entity: [name detected] | Match Requirement linked to removed/missing document | |
| Warning | Flow [Flow name] (Flow ID): Trigger [Trigger name] (Trigger ID): Match Requirement (MR ID): Condition option :C is deprecated and has no effect anymore, it's safe to delete it | Deprecated TLML Syntax option | |
| Warning | Language Object / Entity [Name]: Condition uses undefined Language Object / Entity: [Name] | Learn how to create a new Language Object or an Entity | |
| Warning | Undeclared variable being set: [Variable name]. Add a session/flow/local variable declaration to remove this warning. | Learn how to create Flow and Global Variables | |
| Error | Unexpected error creating engine [Directory missing /usr/local/teneo/domains/studio/temp/(...)/languages/en] | Parsing the solution fails, the Tryout Engine fails | Read more here |
| Error | Unexpected error creating engine [The current account does not contain any CLU settings.] | Parsing the solution fails, the Tryout Engine fails | Check the Account's CLU Settings or, alternatively, make an update in the Class Manager to activate the training of a Learn model. |
TLML syntax errors
The TLML syntax error messages displayed in the Tryout are also displayed in the backstage of Teneo Studio under Suggestions (Solution tab > Optimization > Suggestions) and covers the below listed errors; for more information on how to correct these, please see the Suggestions page, Troubleshooting TLML Syntax or visit the TLML Reference Manual.
- Closing parenthesis directly after operator, read more
- Compound-operator may only be used with single words without options; read more
- Condition options not allowed; read more
- Condition predicate script / variable propagation script not allowed; read more
- Condition terminated incorrectly; read more
- First operand missing; read more
- Incomplete dynamic word condition; read more
- Incomplete successor or topic condition; read more
- Invalid number of quotes; read more
- Missing opening brace; read more
- Missing opening parenthesis; read more
- Missing or invalid option value; read more
- Name of language object / entity is missing; read more
- Operator at invalid location; read more
- Operator expected; read more
- Parenthesis not closed; read more
- Script condition terminated incorrectly; read more
- Successor condition not supported; read more
- Unterminated condition comment; read more
- Whitespace not allowed before opening brace of condition predicate / propagation script; read more
Restart and Reload
The user can Restart a conversation or session in the Tryout to reset, for example, Global variable values in order to keep testing a certain Flow making use of those variables. Reload can be used to recreate the Tryout Engine instance, this allows to reload the entire solution and fetch any changes performed by collaborators which are not automatically loaded into the current Tryout Engine instance although they are visible when opening a document (i.e. a Flow).