Skip to main content
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.

DialNexa Workflow Lead History And Debugging Evidence

The history response is built for debugging one lead.

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.

Review Workflow Lead Counts And Pages

The workflow list’s Leads count shows the number of attached leads. Open a workflow’s Leads view to inspect the table and move through pages. Do not treat the number of rows on the current page as the total enrollment. The Voice call node also identifies the outbound agent for its selected number where available. Check this alongside the lead’s latest call attempt when diagnosing a retry. See List Workflow Leads for API pagination and matching totals.

Call Detail Page

Inspect linked calls.

Application Nodes

Debug action failures.

Statuses

Understand status labels.