Flow Logs

Flow Logs give you a complete trace of every flow execution — which nodes ran, what data was processed, and whether anything failed. This is your go-to tool for debugging issues and understanding how your flows are performing.

Accessing flow logs

There are two ways to access logs:

1. From the Flow List — Click the View Logs action on any flow
2. From the Flow Builder — Click the Logs button in the header

📸

Screenshot: Flow Logs page showing execution list with filters

flow-logs-page.png

1. Navigate to a flow and click View Logs
2. Capture the logs page showing the execution list with status indicators
Save to: static/img/screenshots/chatbot-flows/flow-logs/flow-logs-page.png

Log list

The log list shows all executions for a flow:

Column	What it shows
Phone Number	The customer's phone number
Contact Name	The customer's name (if available)
Triggered By	How the flow was started (keyword, button click, webhook, manual)
Trigger Value	The specific keyword, button ID, or trigger data
Status	Success, Failed, or In Progress
Started At	When the execution began
Duration	How long the execution took
Nodes	Completed nodes / Total nodes

Filters

You can filter the log list using:

Filter	Options
Date range	Start date and end date
Status	Success, Failed, In Progress
Phone number	Search by a specific customer's phone

Execution details

Click on any log entry to see the node-by-node trace — a detailed breakdown of every step in the execution.

📸

Screenshot: Execution detail view showing node-by-node trace

execution-detail.png

1. On the Flow Logs page, click on any execution entry
2. Capture the detail view showing the node trace with statuses and timestamps
Save to: static/img/screenshots/chatbot-flows/flow-logs/execution-detail.png

Each node in the trace shows:

Field	What it means
Node type	The type of node (trigger, message, condition, etc.)
Node label	The name you gave the node
Status	Started, Completed, Failed, or Skipped
Started at	When this node began executing
Completed at	When this node finished
Duration	How long this node took (in milliseconds)
Input data	What data the node received
Output data	What data the node produced
Error message	If failed — what went wrong
Next node	Which node ran next and why

Execution statuses

Status	Meaning
Success	The flow completed successfully — all nodes ran without errors
Failed	One or more nodes failed during execution
In Progress	The flow is still running (waiting for customer response or external call)

Execution statistics

At the top of the logs page, you can see overall statistics:

Stat	What it shows
Total Executions	How many times this flow has run
Completed	Number of successful completions
Failed	Number of failed executions
Unique Users	How many different customers have used this flow
Average Duration	Average time to complete the flow

Troubleshooting with logs

Finding a failed node

1. Open the execution detail
2. Look for nodes with Failed status (highlighted in red)
3. Check the error message and error details for the cause

Common failure reasons

Error	Likely cause	Fix
Template not approved	Template used in the flow is no longer approved	Check template status, use a different template
Outside messaging window	Customer hasn't messaged in 24 hours (non-template message)	Use a Template Message node instead
HTTP Call timeout	External system took too long to respond	Increase timeout or check the external system
Invalid variable	A variable used in a message or condition was empty or wrong	Add validation or fallback values
Script error	Code in a Script node failed	Check the script logic and test with sample data

Checking variable values

The session data snapshot in each node's log shows all the variables at that point in the execution. This is invaluable for debugging:

1. Open the execution detail
2. Click on the node where things went wrong
3. Check the session data to see what values the variables had
4. Compare with what you expected

tip

If a flow isn't triggering at all, check these things first:

1. Is the flow active?
2. Is the trigger keyword not conflicting with another flow?
3. Does the flow have a published version?