Issue resolved, back to normal

nostr:nevent1qqsqqqqpms0nzjzk9gg4g5rxhk3axhrgkerdkkg3nau22udltzhftxqpr9mhxue69uhkcctzda6hytnxd9shg6npvchxxmmd9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7myhlj9

Reply to this note

Please Login to reply.

Discussion

Part of this was a known issue with LND (your intuition was spot-on nostr:npub186tqtnx8nc502veqkguypvzpm5hq53p69qrl8l0hes9c4k8mzrssfk59su)

If you want to see which inflight payments are actually stuck you can do something like this:

lncli listpayments --include_incomplete |

jq -r '

.payments |

.[]

| select(.status == "IN_FLIGHT") |

[.payment_hash, .value_msat, ([.htlcs | .[] | select(.status == "IN_FLIGHT") | .route.total_time_lock ] | max)] |

@tsv

'

Then check that the max route.total_time_lock is in the future

I’m happy that you’re happy🫂