Yeah my question was more like why did this happen? it's not like my node or this peer were out of communication. Like I said we were communicating fine, even forwarding several other HTLCs. I have like 13 routing events with this peer since Jan 13th. And I saw this stuck HTLC for several days before the force close, I was afraid it was going to happen. It seems more like a bug.

Also by analyzing the structure of the transaction, I can see that my output is the `to_remote` (unencumbered one). So why the extra transaction, is labeled as a "sweep" by RTL but I was under the impression that only the `to_local` needed a sweep. So [this](https://mempool.space/tx/e81f080f6c86dcc9bb3c08d651e4252a937d26865e990801636486e190525599#flow=&vin=0) other tx makes no sense to me. 

randombitcoiner

HTLC did not resolve in time, must go on chain via Force Close

Force Close outputs are time locked. Non initiator of the close has a time lock of 1 block. Since there's only one htlc in the close, it's probably not yours. The P2TR output is to your wallet.

https://ellemouton.com/posts/normal-operation-pre-taproot/

bitdevs

Can someone help me understand what happened here?

HTLC did not resolve in time, must go on chain via Force Close

Force Close outputs are time locked. Non initiator of the close has a time lock of 1 block. Since there's only one htlc in the close, it's probably not yours. The P2TR output is to your wallet.

Deep dive: https://ellemouton.com/posts/normal-operation-pre-taproot/