System Log Events
The following events are logged in the System Log.
Where debug is yes, the event is logged only when debug mode is enabled.
Nodes
Node | Event | Parameters |
Log Details |
Debug | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GOTO_NODE |
|
|
Yes |
|||||||||||||||||||
SELECT_CHILD |
|
|
Yes |
|||||||||||||||||||
SELECT_CHILD |
|
|
Yes |
|||||||||||||||||||
EXTERNAL_REQUEST |
|
Expand to show the following:
|
Debug required for log details. Debug not required for parameters. |
|||||||||||||||||||
System Log of the Parent Task |
LINK_TO |
|
|
|
||||||||||||||||||
Logged with every LINK_TO event |
IVA_CHANGE_CHECKED |
|
Expand to show whether an IVA update is required. An IVA update may be required if the child task is using a different business plan from the parent task. See also IVA. |
|
||||||||||||||||||
System Log of the Child Task |
LINK_FROM |
|
|
|
||||||||||||||||||
CALLER_RESPONSE |
|
|
|
|||||||||||||||||||
CALLER_RESPONSE |
|
Where no match is detected from the caller, expand to play a recording of the caller's response. This applies to cloud STT nodes. It applies to form nodes where the form type is custom or open and the provider is Google. For the form node, open form type, Google provider, expand to show the following.
|
|
|||||||||||||||||||
EXTERNAL_REQUEST |
Use this event log for troubleshooting.
|
|
Yes |
Voice Tasks - Nodes and System Events
Action | Event | Parameters | Debug | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
An inbound call is received. The call starts. |
CALL_RECEIVED |
|
|
||||||||
An outbound call connects to the task. |
OUTBOUND_CALL |
|
|
||||||||
The caller hangs up before the task completes. |
CALLER_HANGUP |
|
|
||||||||
The call is transferred. |
CALLER_TRANSFERRED |
|
|
||||||||
The call completes. |
CALL_COMPLETED |
|
|
||||||||
|
CALL_DURATION |
|
|
||||||||
Beep detection is enabled for the task and Studio detects a beep after connecting the call. |
BEEP_DETECTION |
|
|
||||||||
Machine detection is enabled for the task and Studio detects that the call has been initiated or answered by a machine instead of a human. |
MACHINE_DETECTION |
|
|
||||||||
The call completed because the number of nodes processed on the call reached the maximum allowed (10,000 nodes). Perhaps your call flow contains an infinite loop. |
MAX_NODE_LIMIT_VOICE |
|
|
||||||||
TTS_VOICE_CHANGE |
|
Yes |
Messaging Tasks - Nodes and System Events
Logging of events showing Message Text (the content from incoming and outgoing messages) in one of the parameters is dependent on the task properties, system logs setting. See Task Properties - Digital.
Action | Event | Parameters | Debug | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
A chatbot message is received. |
MESSAGE_RECEIVED |
|
|
||||||||
A chatbot task is initiated through a campaign. |
OUTBOUND_MESSAGING |
|
|
||||||||
MESSAGE_SEND |
|
|
|||||||||
MESSAGE_REPLY |
|
|
|||||||||
A message is sent using the conversation node. |
CONVERSATION_QUESTION |
|
|
||||||||
A message is received in response to the message sent using the conversation node. |
CONVERSATION_RESUMED |
|
|
||||||||
The conversation begins. |
CONVERSATION_STARTED |
|
|
||||||||
The conversation completes. |
CONVERSATION_COMPLETED |
|
|
||||||||
The message usage limit is reached. |
MESSAGE_LIMIT |
|
|
Workflow Tasks - System Events
Action | Event | Parameters | Debug |
---|---|---|---|
Execution of the workflow begins. |
WORKFLOW_STARTED |
|
|
Execution of the workflow completes. |
WORKFLOW_COMPLETED |
|
|
The usage limit on the workflow is reached. |
WORKFLOW_LIMIT |
|
|
Functions
Action | Event | Parameters |
Log Details |
Debug | ||||||
---|---|---|---|---|---|---|---|---|---|---|
JAVASCRIPT_FUNCTION_ERROR |
|
Expand to show the JavaScript function ID, function name, and errors. |
|
IVA
Event |
Situation |
Parameters |
Log Details |
Debug | ||||||
---|---|---|---|---|---|---|---|---|---|---|
IVA_CHANGE_CHECKED |
Logged with every LINK_TO event. An IVA update may be required if the child task is using a different business plan from the parent task. |
|
Expand to show whether an IVA update is required. |
|
||||||
IVA_UPDATE_NOT_REQUIRED |
Logged when an IVA update is not required by the child task of a LINK_TO event. |
|
Expand to show the link task ID, session ID, and whether an IVA update is required. |
|
||||||
IVA_UPDATED |
Logged when an IVA update is required by the child task of a LINK_TO event and the IVA update is successful. |
|
Expand to show the session ID. The session ID changes to the business plan of the child task. |
|
||||||
IVA_LIMIT_REACHED |
Logged when an IVA update is required by the child task of a LINK_TO event and the IVA update fails because all IVAs in the targeted IVA plan are in use or insufficient IVAs are available. The call flow continues by skipping the child task. |
|
Expand to show the child task ID and whether the IVA limit is reached. |
|