FiberTraceboxFailure replay infrastructure

Replay Lab

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

Selected trace

trace_be1a0059-2341-45ef-bcde-712b4198e113

Open Trace Detail
trace_5fa35ab8-e68failed · 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_be1a0059-2341-45ef-bcde-712b4198e113

replayed
Amount
0 CKB
Failure time
30ms
Sender
fiber-rpc-node
Receiver
fibt10001p6c...rdgdh9

INVOICE_INVALID

Invoice invalid

The receiver invoice could not be validated before payment execution.

Failed at fiber_rpc_error after 30ms

Failure Timeline

Lifecycle events captured in milliseconds.

5 events
  1. 0ms
    request_receivedinfo

    Live Fiber payment dry-run requested

  2. 20ms
    node_infosuccess

    Connected to Fiber Network Node RPC

  3. 20ms
    channel_snapshotsuccess

    Captured 1 live Fiber channels

  4. 20ms
    graph_snapshotsuccess

    Captured live Fiber graph snapshot

  5. 30ms
    fiber_rpc_errorerror

    InvalidParameter: Failed to validate payment request: "invoice is expired"

Generated Replay Scenarios

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

same_conditionsauto
fresh_invoiceauto

Recommended fix

Request a fresh invoice

Replay confirms the original invoice cannot pass validation under the same conditions and succeeds only after replacing it.

Request a fresh invoice from the receiver and retry with the new payment hash.

Validate invoice expiry, amount, asset, and payee fields before route discovery.

Confidence: highfresh_invoice

Original vs Replay

Original

Failed
Amount
0 CKB
Latency
30ms
Failed at
fiber_rpc_error

Replay

success
What changed
Requested a fresh receiver invoice before retry
Latency
34ms

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.

37ms

fresh_invoice

Requested a fresh receiver invoice before retry

success

A fresh invoice replaces the cancelled or invalid payment hash and gives the sender a valid retry target.

34msSmallest-fix recommendation

Report Export

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

MarkdownJSON
Original
Failed
Replay
Success
Confidence
high