Replay Lab

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

Selected trace

trace_a5c65ebc-ebd5-4d88-a937-835ee5a30fd3

Open Trace Detail

Original failed payment

trace_a5c65ebc-ebd5-4d88-a937-835ee5a30fd3

replayed
Amount
500 CKB
Failure time
84ms
Sender
fiber-devnet-sender-01
Receiver
fiber-devnet-receiver-09

ROUTE_CAPACITY_INSUFFICIENT

Route capacity insufficient

A route was discovered, but the available forwarding capacity was lower than the requested payment amount.

Failed at capacity_probe after 84ms

Failure Timeline

Lifecycle events captured in milliseconds.

6 events
  1. 0ms
    request_receivedinfo

    Payment attempt created for 500 CKB

  2. 8ms
    invoice_validationsuccess

    Invoice fields parsed

  3. 18ms
    route_discoveryinfo

    Candidate routes loaded from sandbox graph

  4. 50ms
    policy_checkinfo

    Route policies evaluated

  5. 62ms
    capacity_probewarning

    Candidate path capacity: 320 CKB available for 500 CKB request

  6. 84ms
    capacity_probeerror

    Route capacity insufficient: max forwardable 320 CKB

Generated Replay Scenarios

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

same_conditionsauto
reduced_amount_80auto
reduced_amount_64auto
increased_outbound_capacityauto
alternate_routeauto
split_paymentauto

Recommended fix

Smallest route-capacity fix

Replay showed the original 500 CKB payment fails, 80% still fails, and a partial payment of 320 CKB succeeds. Splitting over the same static route does not complete the original total; exact outbound capacity repair and an alternate route succeeded.

Send at most 320 CKB now as a partial payment, or add capacity to send the full 500 CKB.

If the operator controls liquidity, add at least 180 CKB outbound route capacity.

Confidence: highreduced_amount_64

Original vs Replay

Original

Failed
Amount
500 CKB
Latency
84ms
Failed at
capacity_probe

Replay

success
What changed
Reduced amount to 64%: 320 CKB
Latency
58ms

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.

91ms

reduced_amount_80

Reduced amount to 80%: 400 CKB

failed

400 CKB still exceeds the constrained route capacity, so the payment fails again.

70ms

reduced_amount_64

Reduced amount to 64%: 320 CKB

success

320 CKB matches the observed maximum forwardable capacity and settles.

58msSmallest-fix recommendation

increased_outbound_capacity

Added exact outbound route capacity deficit: 180 CKB

success

Adding 180 CKB raises route capacity to the original payment amount and removes the constrained hop.

66ms

alternate_route

Selected alternate route excluding the failing condition

success

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

73ms

split_payment

Split payment into 250 CKB + 250 CKB

failed

The route has only 320 CKB total forwardable capacity. After the first part, the same static route cannot carry the second part, so the full 500 CKB payment is not completed.

79ms

Report Export

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

Original
Failed
Replay
Success
Confidence
high