FiberTraceboxFailure replay infrastructure

Replay Lab

Failure replay, route comparison, and smallest-fix evidence.

Selected trace

trace_1acf0526-5bcc-4e11-9d84-d32a934aeb77

Open Trace Detail
trace_246f84bf-5d7replayed · ROUTE_CAPACITY_INSUFFICIENT · 33mstrace_c2bbcf1f-55dreplayed · ROUTE_CAPACITY_INSUFFICIENT · 18mstrace_da028861-8c3replayed · ROUTE_CAPACITY_INSUFFICIENT · 45mstrace_1acf0526-5bcreplayed · PEER_OFFLINE · 73mstrace_5fa35ab8-e68replayed · ROUTE_NOT_FOUND · 61mstrace_cb370d8f-8b7replayed · PEER_OFFLINE · 73mstrace_c2c00847-32freplayed · ROUTE_CAPACITY_INSUFFICIENT · 84mstrace_93cada83-9efreplayed · ROUTE_CAPACITY_INSUFFICIENT · 84mstrace_93aaeba5-812replayed · ROUTE_NOT_FOUND · 61mstrace_be1a0059-234replayed · INVOICE_INVALID · 30mstrace_d0c7e112-854replayed · ROUTE_NOT_FOUND · 2ms

Original failed payment

trace_1acf0526-5bcc-4e11-9d84-d32a934aeb77

replayed
Amount
140 CKB
Failure time
73ms
Sender
fiber-devnet-sender-01
Receiver
fiber-devnet-receiver-09

PEER_OFFLINE

Required peer offline

The payment reached a route execution step that depended on a peer that was not reachable.

Failed at peer_connect after 73ms

Failure Timeline

Lifecycle events captured in milliseconds.

5 events
  1. 0ms
    request_receivedinfo

    Payment attempt created for 140 CKB

  2. 8ms
    invoice_validationsuccess

    Invoice fields parsed

  3. 18ms
    route_discoveryinfo

    Candidate routes loaded from sandbox graph

  4. 39ms
    policy_checkinfo

    Route policies evaluated

  5. 73ms
    peer_connecterror

    Peer offline during route execution

Generated Replay Scenarios

Selected from the failure fingerprint, not manually scripted in the UI.

same_conditionsauto
restored_peerauto
alternate_routeauto
retry_after_delayauto

Recommended fix

Restore peer or route around it

Replay reproduced the offline-peer failure, then succeeded when the peer was restored, when an alternate route avoided it, and after retry delay.

Restore peer reachability, then retry. If restoration is outside your control, route around the peer.

Confidence: highrestored_peer

Original vs Replay

Original

Failed
Amount
140 CKB
Latency
73ms
Failed at
peer_connect

Replay

success
What changed
Restored unreachable peer before retry
Latency
53ms

Replay Evidence

same_conditions

Original amount, route, peer state, fee limit, timeout, and asset unchanged

failed

The original failure reproduces under the same conditions, confirming the fingerprint is stable.

80ms

restored_peer

Restored unreachable peer before retry

success

Restoring peer reachability gives FNN a usable route again.

53msSmallest-fix recommendation

alternate_route

Selected alternate route excluding the failing condition

success

A route with different hops avoids the original failure point with slightly higher latency.

91ms

retry_after_delay

Retried after peer health delay

success

A delayed retry succeeds after the peer returns to the reachable set.

94ms

Report Export

Export the failure timeline, replay evidence, recommendation, and mode disclosure.

MarkdownJSON
Original
Failed
Replay
Success
Confidence
high