Teneo Developers
Table of Contents
Was this page helpful?

Share to

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 typeAffected node/elementError messageImplicationResolution
Critical ErrorClass MatchThis Match does not contain a valid or saved Class referencePrevents Flow saveReview the Class Match to ensure that the Class name is correct; open the Class Manager to add any new Class
Critical ErrorContext MatchA context restriction is missingPrevents Flow saveAdd the missing Context Match to the Intent Trigger or Transition
Entity After MatchThis After Match contains an incomplete mapping. The Source and Target variables must be definedPrevents Flow saveSelect 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 ErrorEntity Match Entity After MatchThis document does not contain a valid Entity referencePrevents Flow saveAdd the missing Entity to the Match or After Match
Critical errorFlow LinkA 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 SolutionCreates Solution inconsistency, Try Out Engine will fail to loadSelect the Flow Link node in the Flow to update the flow reference
ErrorFlow LinkA flow link node is linked to a non-sub-flow and has post transitionsThe 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 errorFlow TriggerThe flow has no triggers and is not a sub-flowPrevents Flow saveEither add an Intent Trigger or convert the Flow into a Sub-flow
Critical errorIntegration nodeA 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 continuingCreates Solution inconsistency, Try Out Engine will fail to loadSelect 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
WarningIntent TriggerThis document contains no MatchesSelect the Intent Trigger in the Flow editor to open the Trigger panel (right-side of the Flow window), add the wanted Matches
Critical ErrorLanguage Object Match Language Object After MatchThis document does not contain a valid Language Object referencePrevents Flow saveAdd the missing Language Object to the Match or After Match
WarningListener After Match Flow ListenerThe listener condition is missingWrite the Listener syntax in the relevant node; the Listener expects a syntax written in the Teneo Linguistic Modeling Language
Output node: Output ParametersThere are duplicate names in the listOutput Parameters need to have unique names; select the Output node and update the name of one of the Output Parameters
InformativeOutput Script Flow Link Junction IntegrationA nodes is unconnected or un-reachableLearn in the Transitions page how to draw a transition
Critical ErrorScript Match Listener After Match Script After MatchNo script is definedPrevents Flow saveWrite the script expression (Groovy) in the relevant node
WarningSyntax MatchThe condition is missingA 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 typeAffected node / elementError messageImplicationResolution
Document validation failedClass MatchA valid class reference is missingPrevents Flow saveAdd the Class reference in the Class Match
ErrorClass MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by either adding a reference to another Class or deleting the Match
Document validation failedEntity After MatchA mapping must define a source variablePrevents Flow saveAdd the mapping in the Data Entity
Document validation failedEntity After MatchA valid entity reference is missingPrevents Flow saveAdd the Entity name in the Data Entity
ErrorEntity After MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the After Match by either adding a reference to another Entity or deleting the After Match; else create the missing Entity again
CriticalEntity After MatchThis Entity After Match has duplicated variable target mappingsAdding two identical Variable Mappings will color the fields in red and prevent Flow save until one of mappings is changedChange the Variable Mapping of one of the mappings to be able to save the Flow.
ErrorEntity After Match - Source and Target Variable MappingThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the After Match by either removing the variable mapping, updating to an existing variable, or by recreating the wanted variable
Document validation failedEntity MatchA valid entity reference is missingPrevents Flow saveAdd the Entity name in the Match Entity
ErrorEntity MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate 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!FlowLOCK_NOT_FOUNDUnsaved changes are lost, user's lock on the document is not foundUnfortunately, 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.
WarningFlowPlease use a different name as this one is already usedOn Flow creation, if another Flow already exists with the same name in the same Folder, this warning is displayedGive the new Flow another name to be able to continue with the creation.
WarningFlowYou have unsaved changes. Are you sure you want to leaveUnsaved changes will be lostClick OK to close the Flow without saving the changes; click Cancel to return to the Flow to save the changes.
Document validation failedFlow LinkA valid flow reference is missingPrevents Flow saveAdd a valid Flow reference in the Call Flow Link
WarningFlow LinkFlow 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 SolutionSolution is invalid (Try Out cannot be started)Add a valid Flow reference in the Call Flow Link
WarningFlow Variable MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by deleting it, or re-create the Flow Variable
WarningGlobal Variable MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by deleting it, or re-create the Global Variable
WarningIntegrationA method must be defined for the IntegrationIntegration node cannot be closed and Flow save is preventedAdd the missing method to the Integration
WarningIntegrationA variable must be assigned to the mappingIntegration node cannot be closed and Flow save is preventedAdd the missing variable in the Integration
WarningIntegrationAn output parameter of the integration must be definedIntegration node cannot be closedAdd the missing output parameter of the Integration
Document validation failedIntegrationThe node is still in edit mode. Close it to confirm the changesPrevents Flow saveClose the Integration node to save the Flow
Document validation failedLanguage Object After MatchA valid language object reference is missingPrevents Flow saveAdd the Language Object name in the Data Language Object
ErrorLanguage Object After MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the After Match by either adding a reference to another Language Object or deleting the After Match; else create the missing Language Object again
CriticalLanguage Object After MatchThis Language Object After Match has duplicated variable target mappingsAdding two identical Variable Mappings will color the fields in red and prevent Flow save until one of mappings is changedChange the Variable Mapping of one of the mappings to be able to save the Flow.
Document validation failedLanguage Object MatchA valid language object reference is missingPrevents Flow saveAdd the Language Object name in the Match Language Object
ErrorLanguage Object MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by either adding a reference to another Language Object or deleting the Match; else create the missing Language Object again
Document validation failedScripted Context MatchA scripted context Match must have at least one state assignedPrevents Flow saveAdd the state of the selected Scripted Context in the Match Context
Document validation failedScripted Context MatchA valid scripted context reference is missingPrevents Flow saveAdd the reference to the Scripted Context in the Match Context
WarningScripted Context MatchThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by deleting it, or re-create the Scripted Context
WarningScripted Context Match - StateThe referenced document cannot be found. It may have been deleted.Prevents Flow saveUpdate the Match by removing the no longer available state
ErrorVarious Flow nodesRemoving this node is not possible as it would leave the flow in an invalid statePrevents deleting the Flow nodeClicking 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