Flow Debug

View detailed execution logs, find, and fix problems in individual flow runs

Flow Debug provides a step-wise execution trace for your recent flow executions. You can find and fix problems in your flows using Flow Debug. This capability is typically meant to be used for troubleshooting purposes while configuring and iterating flows. We recommend you to use Debug Console for viewing old transaction logs.

You can launch the flow debug panel using the Flow Debug icon at the right navigation panel of your flow canvas. The Flow Debug panel opens in a split view at the bottom of your flow and displays a list of 10 most recent flow runs. Typically logs take about two minutes to show in the flow debug section. You may not see the logs for a recently initiated transaction immediately.

  • Click the transaction ID to drill down to the details of each flow run (transaction)
  • Filter the flow executions using the transaction ID
  • Filter the logs based on selected date range and time (Logs are available for the latest 30 days).
1559

Debug - Canvas split view

The information captured within logs is segregated into three levels based on the sensitivity of the data and the level of detail:

  • Level 1: Summary Logs
  • Level 2: Sequence Summary
  • Level 3: Node Execution Details.

You can now see the timezone along with the timestamp in the transaction logs.

1601

Transaction Sequence Summary

This view lists the complete sequence of nodes executed for the selected transaction. It also lists the time taken to execute each step and the outcome of each step. Step here refers to the runtime execution of a particular node. This view allows you to verify the business logic within the flow without going into technical details.

Since navigating to a specific node in a large flow can be cumbersome, flow debug automatically shifts the canvas to the respective node when you click on a node name under the 'Node' column.

🚧

Encryption

Summary logs do not contain personally identifiable information (PII) and are therefore not encrypted. However, the details of node execution may contain PII, in which case such information is encrypted. Only users who are authorized by the client admin can decrypt these detailed logs to view them in plain text.

Node Execution Details

The node execution details are available only to users authorized by the tenant onwer. This view, by default, shows PII in encrypted form. However, basic information such as the outcome of the node and the execution parameters like start time is available to all users in plain text.

πŸ“˜

Note

For all the flows created after the v6.3.0 release, there is a limit of 1000 for the number of node executions within a single flow. If the number of node executions exceeds 1000, the node execution fails with an error β€œSystem limit reached.”

❗️

Capturing Node Execution Details during Initial Set-up.

You must enable the Descriptive Logs option under flow settings to capture node execution details. Please note that this feature is suggested to be used only during initial flow set-up and troubleshooting. Enabling this feature in production mode can impact your tenant performance.

800

Node Level Execution Details

In the case of voice flows, you can see the various voice nodes within the flow and the sequence in which the nodes are executed. If the flow contains the voice node group, then you can drill down to the individual nodes in the group.

When a voice flow has recordings, you can click Recordings to play the recordings directly in the debug console. You can also see the call duration and audio prompts configured and played to the caller during an ongoing call.


1601

Voice Flows

Transaction Logs

  • Decrypts Logs: the additional description of the action performed by the node under the transaction in encrypted mode.
  • Time Stamp: the time at which the flow execution started
  • Transaction ID: the ID number created for the transaction
  • Invoked By: the trigger that invoked the flow
  • Time Taken: the time taken to execute the entire flow
  • Last Node: the last node that was in use when the flow ended
  • NodeID : ID of the current node in the flow
  • Outcome: the node event of each node
  • Details: details of the node execution.

πŸ‘

As mentioned above, flow debug allows you to analyse step wise execution of your recent flow executions and is mainly best suited for understanding how your flow is progressing and where there are issues, if any, during initial flow configuration and prototyping phases. If you want to analyse a transaction within last 30 days period, or want to look at the past 30 days of message exchanges for a given customer or channel, you can use Debug Console feature.

Transaction Channels

The following parameters are displayed in the Debug flow of the Start Node:

ChannelEvent in Start nodeParameters to be shown in transaction logs
SMSMobile originated -MOTimestamp
Sender Number
Service Number
Message
SMSOn Link clickTimestamp
Sender Number
VoiceInbound callService Number
Timestamp
MSISDN
VoiceMissed callService Number
Timestamp
MSISDN
MMSMobile originated -MOSender Number
MessengerIncoming MessageAppId
PSID
Message
Attachment URL
Timestamp
Location URL
MessengerOn link clickAppId
PSID
Tim_estamp
MessengerPostbackAppId
PSID
Timestamp
Post_back Payload
WhatsAppIncoming MessageAppId
WaId
Timestamp
Message
Image URL
Location URL
Voice URL
Audio URL
Video URL
Sticker URL
WhatsAppPostbackAppId
WaId
Timestamp
Button Payload
WhatsAppList MessageAppId
WaId
Timestamp
List Description
Row Title
Row Identifier
WhatsApp

Reply button Message
AppId
WaId
Timestamp
Reply Button Title
Reply Button Identifier
In-App / Live ChatCustom eventUserId
PushId
Timestamp
AppId
In-App / Live ChatGeo enterUserId
PushId
Timestamp
AppId
GeofenceId
In-App / Live ChatGeo LeaveUserId
PushId
Timestamp
AppId
GeofenceId
In-App / Live ChatIncoming MessageTimestamp
UserId
PushId
Message
Attachments
DeviceId
Version
Threadid
In-App / Live ChatOn thread closeThreadid
AppId
UserId
In-App / Live ChatOn postbackTimestamp
UserId
PushId
Message
Attachments
DeviceId
Version
ThreadId
Button Payload
EmailIncoming MessageMessage
Emailid
AppId
To Address
Attachments
Receipts
Timestamp
EmailSubscribeEmailid
AppId
Attachments
Timestamp
EmailunsubscribeEmailId
AppId
Attachments
Timestamp
RCSIncoming MessageText
Timestamp
AppId
Number
RCSMessage
Incoming attachment
Text
Timestamp
AppId
Number
File URL
RCSLocation responseText
Timestamp
AppId
Number
RCSPostbackText
Timestamp
AppId
Number
Postback Data
Apple Messages for BusinessConversation closedABCUserId
AppId
Apple Messages for BusinessInteractive Message authenticationAppId
AuthToken
AuthStatus
Apple Messages for BusinessInteractive Message list pickerABCUserId
AppId
Timestamp
Date Picker Time Slot
Date Picker Duration
Time Slot Identifier
Time Slot Start Time
List Picker Items
List Picker Other Items
Apple Messages for BusinessInteractive Message paymentABCUserId
AppId
Timestamp
Payment Status
Apple Messages for BusinessIncoming MessageABCUserId
AppId
Timestamp
Message
Attachment URL
Apple Messages for BusinessInteractive Message quick replyABCUserId
AppId
Timestamp
Selected Identifier
Selected Index
Apple Messages for BusinessInteractive Message form responseABCUserId
AppId
Timestamp
Selections
Selections Count
Apple Messages for BusinessTyping indicatorABCUserId
AppIdAppId
Type
Apple Messages for BusinessInteractive Message new authenticationAppId
AuthToken
AuthStatus
Apple Messages for BusinessInteractive Message iMessage extensionAppId
URL
Custom eventPayload
Timestamp
Google Business MessagesIncoming MessageAppId
ConversationId
AgentId
Send Time
MessageId
Text
Google Business MessagesUser StatusAppId
ConversationId
AgentId
Send Time
IsTyping
Requested Live Agent
Google Business MessagesSurvey ResponseAppId
ConversationId
AgentId
Send Time
SurveyId
Question Response Text
Question Response Postback Data
QuestionIndex
Google Business MessagesSuggestion ResponseAppId
ConversationId
AgentId
Send Time
MessageId
Postback Data
Text
Suggestion Type
InstagramIncoming MessageMessageId
Igsid
Igid
Timestamp
UserId
AppId
Message Type
Attachment Type
Attachment Url
Story Reply Url
Replied MessageId
InstagramMessage DeletedMessageId
Igsid
Igid
Timestamp
UserId
AppId
IsDeleted
InstagramPostbackMessageId
Igsid
Igid
Timestamp
UserId
AppId
Payload
Title
Quick Reply Payload

Inbound events

The following parameters are displayed in the Debug flow of the Receive Node:

ChannelEvents in Receive nodeParameters to be shown in transaction logs
SMS

Β·
Sender Number
Service Number
Message
Attachment
Timestamp
VoiceMSISDN
Service Number
Message
Timestamp
MessengerIncoming MessagePSID
AppId
Message
Attachments
Timestamp
MessengerPostbackPSID
AppId
Payload
Timestamp
WhatsAppIncoming MessageAppId
WaId
Timestamp
Message
Image URL
Location URL
Voice URL
Audio URL
Video URLSticker URL
WhatsAppPostbackAppId
WaId
Timestamp
Button Payload
WhatsAppList MessageAppId
WaId
Timestamp
List Description
Row Title Row Identifier
WhatsAppReply button MessageAppId
WaId
Timestamp
Reply Button Title
Reply Button Identifier
Custom eventPayload
In-App / Live ChatIncoming MessageTimestamp
UserId
PushId
Message
Attachments
DeviceId
Version
ThreadId
In-App / Live ChatForm responseTimestamp
UserId
PushId
Form Response
Attachments
DeviceIdVersion
ThreadId
In-App / Live ChatPostbackTimestamp
UserId
PushId
Message
Attachments
DeviceId
Version
ThreadId
Button Payload
Apple Messages for BusinessInteractive Message Time pickerABCUserId
AppId
Timestamp
Message
Attachment URL
Date Picker Timeslot
Date Picker Duration
Time Slot Identifier
Time Slot Start Time
Apple Messages for BusinessInteractive Message authenticationAuthToken
AuthStatus
Apple Messages for BusinessInteractive Message list pickerABCUserId
AppId
Timestamp
List Picker Items
List Picker Other Items
Apple Messages for BusinessInteractive Message paymentABCUserId
AppId
Timestamp
Payment Status
Apple Messages for BusinessInteractive Message form responseABCUserId
AppId
Timestamp
Selections
Selections Count
Apple Messages for BusinessConversation closedABCUserId
AppId
Apple Messages for Business Interactive Message new authenticationAppId
AuthToken
AuthStatus
Apple Messages for BusinessInteractive Message quick replyABCUserId
AppId
Timestamp
Selected Identifier
Selected Index
Apple Messages for Business Typing indicatorABCUserId
AppId
Type
Apple Messages for BusinessInteractive Message iMessage extensionAppId
URL
Apple Messages for Business Incoming MessageABCUserId
AppId
Timestamp
Message
Attachment URL
RCSIncoming attachmentText
Timestamp
AppId
Number
RCS Incoming MessageText
Timestamp
AppId
Number
File URL
RCSLocation responseText
Timestamp
AppId
Number
RCS PostbackText
Timestamp
AppId
Number
Postback Data

HTTP node logs

For HTTP nodes, the flow transactions logs are:

  • Request Timestamp
  • Request URL
  • Request Data
  • Response timestamp
  • Response Data

Custom node logs

For Custom nodes, the flow transactions logs are:

  • Request timestamp
  • Request URL
  • Request Data
  • Response timestamp
  • Response Data

πŸ“˜

Transaction details for Custom event/Webhook is available for a maximum of 7 days.

Prebuilt Transaction Details - Outbound and Async events

For Prebuilt nodes, the flow transactions logs are:

  • Resume key
  • Request timestamp
  • Request URL
  • Request Data
  • Response timestamp
  • Response Data

Variables Created or Updated during the Node Execution

Webex Connect logs the list of the variables created or updated in node executions for all flow transactions under the 'Variables created/updated during node execution' section as shown below. The parameters which meet one of the following conditions will be listed in this section:

  • A variable is one of the Output variables of the node and it is used in later part of the flow (mentioned as a variable in the configuration of other nodes).
  • The value of the variable used in the node execution is updated after it is used in the previous node.

πŸ“˜

Note

These logs are generated only when Descriptive logs are not enabled.

πŸ“˜

Note

Variables created as an object in Evaluate node are replaced in the logs with values received from Rhino engine.

Example -var Array_vechicle = ['Car', β€˜Bike’, β€˜Ship’];

The value captured in the logs for Array_vechicle: org.mozilla.javascript.NativeArray@99582cf denoting the Array_vechicle is a native array in the Evaluate node script.

The screenshot below is an example of the transaction log from the Receive node:

Receive Node - Transaction Logs

Receive Node - Transaction Log