FC due to Fulfilled HTLC $ID SENT_REMOVE_HTLC cltv $CLTV hit deadline without attempt to claim #8899
Description
Just had a CLN node FC on me by broadcasting the commitment suggesting it hit the CLTV deadline but it didn't try to fulfill the HTLC and we were connected. Is there maybe some missing delay that led the downstream to provide the preimage but CLN immediately FC'd rather than providing the preimage upstream first?
All the (non-gossip, non-ping, non-pong) messages from my side:
2026-02-12 19:07:29.456 TRACE [lightning::ln::peer_handler:1719] Enqueueing message UpdateAddHTLC { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, htlc_id: 97897, amount_msat: XXX, payment_hash: XXX, cltv_expiry: 936281, skimmed_fee_msat: None, onion_routing_packet: OnionPacket version 0 with hmac [XXX], blinding_point: None, hold_htlc: None } to 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:07:29.456 TRACE [lightning::ln::peer_handler:1719] Enqueueing message CommitmentSigned { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, signature: XXX, htlc_signatures: [XXX], funding_txid: Some(8b4b97766837ed0e4a6bf0c84b698a3858fe8c40e1c1cef74b4fba3605bd942e) } to 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:07:30.056 TRACE [lightning::ln::peer_handler:2400] Received message RevokeAndACK(RevokeAndACK { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, per_commitment_secret: [XXX], next_per_commitment_point: PublicKey(XXX), release_htlc_message_paths: [] }) from 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:07:30.220 TRACE [lightning::ln::peer_handler:2400] Received message CommitmentSigned(CommitmentSigned { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, signature: XXX, htlc_signatures: [XXX], funding_txid: None }) from 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:07:30.237 TRACE [lightning::ln::peer_handler:1719] Enqueueing message RevokeAndACK { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, per_commitment_secret: [XXX], next_per_commitment_point: PublicKey(XXX), release_htlc_message_paths: [] } to 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
followed by regular ping/pongs every 10 seconds, until...
2026-02-12 19:16:31.883 TRACE [lightning::ln::peer_handler:1719] Enqueueing message ErrorMessage { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, data: "Channel closed because commitment or closing transaction was confirmed on chain." } to 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:16:32.274 TRACE [lightning::ln::peer_handler:2400] Received message Error(ErrorMessage { channel_id: 2e94bd0536ba4f4bf7cec1e1408cfe58388a694bc8f06b4a0eed376876974b8b, data: "Fulfilled HTLC 97897 SENT_REMOVE_HTLC cltv 936281 hit deadline" }) from 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5
2026-02-12 19:16:32.274 TRACE [lightning::ln::peer_handler:3438] Handling disconnection of peer 03e9e5a2ae70e42d012c2cecc5a2662630b97efeb13c4080168e19f23a518051c5 because the socket was disconnected