> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/workflow-voice-call-node-leads.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=2c4d698b855ecb056134c09ff32fcad4" alt="DialNexa workflow lead history panel showing completed Voice Call node evidence, call IDs, transition reason, and lead variables." style={{ width: '100%', maxWidth: '1100px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="3420" height="1850" data-path="images/documentation/screenshots/workflow-voice-call-node-leads.png" />

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

## 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.

<CardGroup cols={2}>
  <Card title="Visited nodes" icon="map-pin" href="/workflows/builder-concepts">
    Shows which nodes the lead entered.
  </Card>

  <Card title="Traversed edges" icon="route" href="/workflows/condition-nodes">
    Shows which edge labels were followed.
  </Card>

  <Card title="Current node" icon="locate-fixed" href="/workflows/workflow-statuses">
    Shows where an active lead is waiting or processing.
  </Card>

  <Card title="Call details" icon="phone-call" href="/monitoring/call-detail-page">
    Links voice call transitions to call logs.
  </Card>
</CardGroup>

## Debug A Stuck Lead

<Steps>
  <Step title="Open lead history">
    Start with the lead, not the whole workflow.
  </Step>

  <Step title="Find current node">
    Check whether the lead is at a call, wait, condition, application, converted, or dropped node.
  </Step>

  <Step title="Read the last transition">
    Look at reason and metadata for the latest move.
  </Step>

  <Step title="Open linked call log">
    If the last node was a Voice Call node, inspect the exact call.
  </Step>

  <Step title="Fix the node config">
    Adjust outputs, variables, or integration setup, then retest with a small sample.
  </Step>
</Steps>

## Related Reading

<CardGroup cols={2}>
  <Card title="Call Detail Page" icon="panel-right" href="/monitoring/call-detail-page">
    Inspect linked calls.
  </Card>

  <Card title="Application Nodes" icon="plug" href="/workflows/application-nodes">
    Debug action failures.
  </Card>

  <Card title="Statuses" icon="list" href="/reference/statuses">
    Understand status labels.
  </Card>
</CardGroup>