Definition #
Path and Gate Troubleshooting is a focused diagnostic process for routing logic errors, progression breaks, and outcome mismatches.
Why it matters #
Routing issues can silently affect many candidates.
Fast diagnosis protects conversion quality and operational trust.
How it works #
- Reproduce with deterministic input.
- Trace step data writes.
- Inspect gate rule evaluation order.
- Confirm selected target path/outcome.
- Validate post-route rendering and completion behavior.
Configuration fields #
- Candidate id/token
- Agent id, path id, gate id
- Rule set snapshot and priority
- Runtime input values
- Route target result
- Fallback status
- Timestamp window for logs
Example scenario #
A candidate should go to “Qualified Path” but lands in “Nurture Path.”
Investigation finds rule priority changed, causing a broad condition to match first.
Common mistakes #
- Testing with inconsistent candidate state
- Reading stale values due to missing refresh
- Misordered gate rules
- Comparing strings vs numbers incorrectly
- No fallback route instrumentation
Troubleshooting checklist #
- Reproduce with fresh test candidate
- Capture raw values before gate evaluation
- Verify rule order and first-match behavior
- Confirm selected target in logs
- Validate fallback logic explicitly
- Re-test all high-traffic branches after fix