The flow designer checks the flow after every change. The findings appear in the Error list below the canvas, and the affected nodes get a colored frame: red for errors, orange for warnings, green or khaki for information messages.
- Each row shows the severity, code, message and the affected item, for example the node.
- Clicking the row selects the node; if the row concerns the flow, the designer shows the flow properties.
- Double-clicking an error in the code opens the code editor.
What prevents saving
Most errors still allow saving; the flow then appears in the list with the status Errors and a red icon. The flow is not saved if there is a critical error:
- Duplicate flowmapping numbers.,
- a flow without a name,
- a second Queue Exit Event,
- Missing element — a required setting is missing,
- errors in custom code, see Code in flows.
The Critical Error window then reports Cannot save flow because of critical errors, the findings and Please fix these errors to make saving possible.
All messages
| Code | Message | Severity | Meaning |
|---|---|---|---|
| FL0001 | Number of start nodes is not equal 1. | error | Every flow needs exactly one Start node. |
| FL0002 | Unconnected start node. Normal start path must be set. | error | In a call flow, Inbound call must be connected. |
| FL0002 | Unconnected node detected. Flow will never execute this node. | warning | No path leads to this node. |
| FL0002 | Flow has an open end! | error | A path stops at a node that is not an end node. Paths from State Change Event and End Event are exempt. |
| FL0002 | Loop was detected in flow | information | A path leads back to an earlier node, for example a menu that repeats. |
| FL0002 | Infinite loop was detected in flow! | error or warning | A loop has no way out to an end node. |
| FL0003 | Invalid parameter detected | warning or error | A setting on the node is empty or wrong; the details name it, for example '…' in '…' is empty. This node may be ignored because of that. or Variable '…' in '…' is invalid or does not exist. Separate email addresses with commas, not semicolons. |
| FL0004 | Duplicate flowmapping numbers. | error, critical | see Mapping |
| FL0005 | Please add a name to this flow | error, critical | The flow has no name. |
| FL0006 | Flow names must be unique, Variable names must be unique, Node names must be unique, Timer names must be unique | error | A name occurs twice. |
| FL0006 | Name is invalid. | error | A name of a flow, variable or function begins with a digit or contains special characters; for variables and functions, also spaces. |
| FL0007 | You can only have one ExitQueueEventNode per Flow. and the corresponding messages for the other event nodes | error; critical for the Queue Exit Event | Each event node can occur at most once. |
| FL0008 | Missing element | error, critical | A required setting is missing, for example the language in Set Language, the media case of a keypad prompt, the recipient for the Transfer error behavior or the media case of an error announcement. |
| FL0008 | No waiting music selected, Boilerplate is not available in all languages, The variable … in boilerplate "…" in language "…" is not available in this flow | warning | A setting is missing, but the flow still runs without it. |
| FL0008 | Unconnected output 'Timeout'. In case of timeout, flow can not continue. | error | Connect Timeout. |
| FL0008 | Unconnected output 'Not Recognized'. In case of not recognized, flow can not continue. | error | Connect Not Recognized. |
| FL0008 | Unconnected output 'Virtual call'. In case of dialin, call will not be handled. | warning | The flow offers a callback or dial-in, but Virtual call at Start is not connected. |
| FL0009 | Queue is not reached | warning or error | The Virtual call path or a path after Holiday closed, Out of business hours or Manual closed does not lead to the queue. |
| FL0009 | Queue is entered from invalid path, Node is not allowed to end in queue node | error | Only the path from Start leads to the queue, see Events and timers. |
| FL0009 | Invalid node in end event path | error | see End Event |
| FL0009 | Invalid node in virtual start path | error | There is a Virtual queue in the Virtual call path. |
| FL0010 | No skill selected, No language selected | error | Not every mapping has a skill or a language, and not every path before it contains Set Skill or Set Language. The designer checks the language only in call flows. |
| FL0011 | Customer recording needs authorization | warning | Start Recording records the customer, but Allow recording is missing in the flow. |
| FL0011 | Missing node | warning | Virtual call is connected, but the flow offers neither a callback nor a dial-in. |
| FL0012 | There is a new version of this flow node, please replace it. | error | Delete the node and insert it again. |
| UC0001–UC0003 | errors in custom code | error, critical | see Code in flows |
| – | Call will be activated immediately. or Call will be activated when connected to an agent. | information | when the call is answered, see In operation |
| – | Error during flow check, please restart the flow editor. | error | The check itself has failed; close the designer and open the flow again. |
Saving
Save sends the flow to the server. The server
- creates a new version with the time and your name,
- passes the flow on to a standby server, to all Administrations and to all Routing Services.
There is no separate confirmation; the list shows the new status. If you have not changed anything, Save sends nothing. If saving fails on the server, the Administration reports Saving flow failed!.
Versions
Every save creates a version. History in the ribbon lists them, newest first, with the time and the administrator. A click loads the name, description and flow logic of that version into the designer; the mappings stay as they are. The old version is only saved when you click Save — as a new version.
Versions are not deleted automatically, only together with the flow or with New.
Testing
There is no test run in the designer. You test with real calls, emails or chats to a mapped number, ideally to a dedicated test number or test mailbox. Helpful tools:
- Generate Code — shows what the flow executes in the Routing Service.
- The Routing Service log with the areas Flow and FlowDesign, see Tracing Settings.
- Running conversations in the Administration show which state a conversation is currently in, see Running conversations.