Workflow Lead History And Debugging In DialNexa

Debug DialNexa workflow lead history with visited nodes, traversed edges, current node, call ids, transition reasons, metadata, and call log links.

Workflow lead history in DialNexa shows the actual path one lead followed through a workflow. It includes the lead, current execution state, all nodes, all edges, visited nodes, traversed edges, transition reasons, metadata, and call ids for voice call nodes.

The workflow canvas tells you what should happen. Lead history tells you what did happen. The second one wins arguments.

Lead History Evidence

The history response is built for debugging one lead.

Evidence	Why it matters
lead	Phone number, dynamic variables, notes, and lead id.
execution	Current node id and execution status.
history	Ordered transitions with from node, to node, reason, timestamp, and metadata.
all_nodes	Full workflow graph, including nodes the lead did not visit.
all_edges	Full workflow structure with labels.
call_id metadata	Links a Voice Call node transition to the exact call log.

How The History Graph Helps

The history view highlights actual execution.

Visited nodes

Shows which nodes the lead entered.

Traversed edges

Shows which edge labels were followed.

Current node

Shows where an active lead is waiting or processing.

Call details

Links voice call transitions to call logs.

Debug A Stuck Lead

1. Open lead history

   Start with the lead, not the whole workflow.

2. Find current node

   Check whether the lead is at a call, wait, condition, application, converted, or dropped node.

3. Read the last transition

   Look at reason and metadata for the latest move.

4. Open linked call log

   If the last node was a Voice Call node, inspect the exact call.

5. Fix the node config

   Adjust outputs, variables, or integration setup, then retest with a small sample.

Related Reading

Call Detail Page

Inspect linked calls.

Application Nodes

Debug action failures.

Statuses

Understand status labels.