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 |