Replay Lab
Failure replay, route comparison, and smallest-fix evidence.
Selected trace
trace_5fa35ab8-e687-4f9f-9798-f766397174e6
Original failed payment
trace_5fa35ab8-e687-4f9f-9798-f766397174e6
- Amount
- 250 CKB
- Failure time
- 61ms
- Sender
- fiber-devnet-sender-01
- Receiver
- fiber-devnet-receiver-09
ROUTE_NOT_FOUND
No viable route found
Route discovery could not find a path from sender to receiver under the current topology and policy filters.
Failure Timeline
Lifecycle events captured in milliseconds.
- 0msrequest_receivedinfo
Payment attempt created for 250 CKB
- 8msinvoice_validationsuccess
Invoice fields parsed
- 18msroute_discoveryinfo
Candidate routes loaded from sandbox graph
- 27mspolicy_checkinfo
Route policies evaluated
- 61msroute_discoveryerror
Route not found after graph search
Generated Replay Scenarios
Selected from the failure fingerprint, not manually scripted in the UI.
Recommended fix
Smallest successful replay change
Selected alternate route excluding the failing condition was the smallest successful replay change.
Selected alternate route excluding the failing condition
Original vs Replay
Original
Failed- Amount
- 250 CKB
- Latency
- 61ms
- Failed at
- route_discovery
Replay
success- What changed
- Selected alternate route excluding the failing condition
- Latency
- 73ms
Replay Evidence
same_conditions
Original amount, route, peer state, fee limit, timeout, and asset unchanged
The original failure reproduces under the same conditions, confirming the fingerprint is stable.
alternate_route
Selected alternate route excluding the failing condition
A route with different hops avoids the original failure point with slightly higher latency.
split_payment
Split payment into 125 CKB + 125 CKB
Split payment does not resolve this failure fingerprint.
Report Export
Export the failure timeline, replay evidence, recommendation, and mode disclosure.