Troubleshooting
Flow
While working in Flows errors and warnings might be displayed in Teneo Studio due to various reasons, this page takes the user through the most common errors and provides additional information as well as suggestions for resolutions and, when relevant, links to more information.
The Errors panel in a Flow displays errors, warnings and informative messages when these are detected in the Flow; clicking the arrow button next to a listed item takes the user to the location in the Flow which the message refers to; the below table captures various types of these messages and provide relevant information for the user to resolve the message.
Having problems with the TLML syntax? Check out the Troubleshooting TLML Syntax page
| Error type | Affected node/element | Error message | Implication | Resolution |
|---|---|---|---|---|
| Critical Error | Class Match | This Match does not contain a valid or saved Class reference | Prevents Flow save | Review the Class Match to ensure that the Class name is correct; open the Class Manager to add any new Class |
| Critical Error | Context Match | A context restriction is missing | Prevents Flow save | Add the missing Context Match to the Intent Trigger or Transition |
| Entity After Match | This After Match contains an incomplete mapping. The Source and Target variables must be defined | Prevents Flow save | Select the trigger or transition in the Flow editor to expand the right-side panel, under the After Match select the missing source and target values | |
| Critical Error | Entity Match Entity After Match | This document does not contain a valid Entity reference | Prevents Flow save | Add the missing Entity to the Match or After Match |
| Critical error | Flow Link | A flow link node cannot find the referenced flow. It may have been deleted or has not been updated from the Master Solution if this is a Local Solution | Creates Solution inconsistency, Try Out Engine will fail to load | Select the Flow Link node in the Flow to update the flow reference |
| Error | Flow Link | A flow link node is linked to a non-sub-flow and has post transitions | The control of the linked child Flow will not be returned to the original parent Flow after execution of the child Flow, and hence the following transitions will never be reached; turn the child Flow into a Sub-flow or delete the transitions following the Flow link node | |
| Critical error | Flow Trigger | The flow has no triggers and is not a sub-flow | Prevents Flow save | Either add an Intent Trigger or convert the Flow into a Sub-flow |
| Critical error | Integration node | A referenced integration definition is missing. The integration may have been deleted or if this is a Local Solution, it may have been added in a Master Solution and should be updated from My Work before continuing | Creates Solution inconsistency, Try Out Engine will fail to load | Select the Integration node to add an Integration previously set up in the Integration manager; or visit the page on Localization setup to learn how to accept changes from a Master solution |
| Warning | Intent Trigger | This document contains no Matches | Select the Intent Trigger in the Flow editor to open the Trigger panel (right-side of the Flow window), add the wanted Matches | |
| Critical Error | Language Object Match Language Object After Match | This document does not contain a valid Language Object reference | Prevents Flow save | Add the missing Language Object to the Match or After Match |
| Warning | Listener After Match Flow Listener | The listener condition is missing | Write the Listener syntax in the relevant node; the Listener expects a syntax written in the Teneo Linguistic Modeling Language | |
| Output node: Output Parameters | There are duplicate names in the list | Output Parameters need to have unique names; select the Output node and update the name of one of the Output Parameters | ||
| Informative | Output Script Flow Link Junction Integration | A nodes is unconnected or un-reachable | Learn in the Transitions page how to draw a transition | |
| Critical Error | Script Match Listener After Match Script After Match | No script is defined | Prevents Flow save | Write the script expression (Groovy) in the relevant node |
| Warning | Syntax Match | The condition is missing | A Syntax Match needs to contain a syntax written in the Teneo Linguistic Modeling Language |
Teneo Studio performs error detection and document validation in Flows, and when errors are detected the field or node of the error is highlighted in red and - in some cases - the user is prevented from saving the Flow until the error is resolved; hovering over an affected node/element displays an Issues message with more information to the user.
The below table captures various types of errors and provide relevant information for the user to resolve the error.
Having problems with the TLML syntax? Check out the Troubleshooting TLML Syntax page
| Error type | Affected node / element | Error message | Implication | Resolution |
|---|---|---|---|---|
| Document validation failed | Class Match | A valid class reference is missing | Prevents Flow save | Add the Class reference in the Class Match |
| Error | Class Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by either adding a reference to another Class or deleting the Match |
| Document validation failed | Entity After Match | A mapping must define a source variable | Prevents Flow save | Add the mapping in the Data Entity |
| Document validation failed | Entity After Match | A valid entity reference is missing | Prevents Flow save | Add the Entity name in the Data Entity |
| Error | Entity After Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the After Match by either adding a reference to another Entity or deleting the After Match; else create the missing Entity again |
| Critical | Entity After Match | This Entity After Match has duplicated variable target mappings | Adding two identical Variable Mappings will color the fields in red and prevent Flow save until one of mappings is changed | Change the Variable Mapping of one of the mappings to be able to save the Flow. |
| Error | Entity After Match - Source and Target Variable Mapping | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the After Match by either removing the variable mapping, updating to an existing variable, or by recreating the wanted variable |
| Document validation failed | Entity Match | A valid entity reference is missing | Prevents Flow save | Add the Entity name in the Match Entity |
| Error | Entity Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by either adding a reference to another Entity or deleting the Match; else create the missing Entity again |
| An error was encountered when saving the document! | Flow | LOCK_NOT_FOUND | Unsaved changes are lost, user's lock on the document is not found | Unfortunately, the only thing to do is to reload Teneo Studio Web to ensure that the lock is applied correctly and hence the changes in the document needs to be applied once more. |
| Warning | Flow | Please use a different name as this one is already used | On Flow creation, if another Flow already exists with the same name in the same Folder, this warning is displayed | Give the new Flow another name to be able to continue with the creation. |
| Warning | Flow | You have unsaved changes. Are you sure you want to leave | Unsaved changes will be lost | Click OK to close the Flow without saving the changes; click Cancel to return to the Flow to save the changes. |
| Document validation failed | Flow Link | A valid flow reference is missing | Prevents Flow save | Add a valid Flow reference in the Call Flow Link |
| Warning | Flow Link | Flow link node cannot find the referenced flow. It may have been deleted or has not been updated from the Master Solution if this is a Local Solution | Solution is invalid (Try Out cannot be started) | Add a valid Flow reference in the Call Flow Link |
| Warning | Flow Variable Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by deleting it, or re-create the Flow Variable |
| Warning | Global Variable Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by deleting it, or re-create the Global Variable |
| Warning | Integration | A method must be defined for the Integration | Integration node cannot be closed and Flow save is prevented | Add the missing method to the Integration |
| Warning | Integration | A variable must be assigned to the mapping | Integration node cannot be closed and Flow save is prevented | Add the missing variable in the Integration |
| Warning | Integration | An output parameter of the integration must be defined | Integration node cannot be closed | Add the missing output parameter of the Integration |
| Document validation failed | Integration | The node is still in edit mode. Close it to confirm the changes | Prevents Flow save | Close the Integration node to save the Flow |
| Document validation failed | Language Object After Match | A valid language object reference is missing | Prevents Flow save | Add the Language Object name in the Data Language Object |
| Error | Language Object After Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the After Match by either adding a reference to another Language Object or deleting the After Match; else create the missing Language Object again |
| Critical | Language Object After Match | This Language Object After Match has duplicated variable target mappings | Adding two identical Variable Mappings will color the fields in red and prevent Flow save until one of mappings is changed | Change the Variable Mapping of one of the mappings to be able to save the Flow. |
| Document validation failed | Language Object Match | A valid language object reference is missing | Prevents Flow save | Add the Language Object name in the Match Language Object |
| Error | Language Object Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by either adding a reference to another Language Object or deleting the Match; else create the missing Language Object again |
| Document validation failed | Scripted Context Match | A scripted context Match must have at least one state assigned | Prevents Flow save | Add the state of the selected Scripted Context in the Match Context |
| Document validation failed | Scripted Context Match | A valid scripted context reference is missing | Prevents Flow save | Add the reference to the Scripted Context in the Match Context |
| Warning | Scripted Context Match | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by deleting it, or re-create the Scripted Context |
| Warning | Scripted Context Match - State | The referenced document cannot be found. It may have been deleted. | Prevents Flow save | Update the Match by removing the no longer available state |
| Error | Various Flow nodes | Removing this node is not possible as it would leave the flow in an invalid state | Prevents deleting the Flow node | Clicking OK takes the user back to the Flow without deleting the Flow node; if the Flow node is really not needed other nodes might need to be connected by drawing them manually before attempting the deletion again; read more |