channel identified by LND as one of the "pending_force_closing_channels", but close channel transaction has been confirmed

[kingpalethe]

I am running the latest versions of bitcoind and lnd

Running into something I can't explain.

Here is the current output of lncli pendingchannels

"pending_force_closing_channels": [
        {
            "channel": {
                "remote_node_pub": "037659a0ac8eb3b8d0a720114efc861d3a940382dcfa1403746b4f8f6b2e8810ba",
                "channel_point": "3c48e584920ac39d2868f0c466e20fc811afae81cd5911b709ec9183064bceb6:0",
                "capacity": "500000",
                "local_balance": "5490",
                "remote_balance": "490032",
                "local_chan_reserve_sat": "0",
                "remote_chan_reserve_sat": "0",
                "initiator": "INITIATOR_LOCAL",
                "commitment_type": "ANCHORS",
                "num_forwarding_packages": "0",
                "chan_status_flags": "",
                "private": false,
                "memo": ""
            },
            "closing_txid": "f7b6fe0c4958e5ad303dab547143d3a7354d9945950cbe217773f9f487448296",
            "limbo_balance": "5490",
            "maturity_height": 823499,
            "blocks_til_maturity": -916,
            "recovered_balance": "330",
            "pending_htlcs": [],
            "anchor": "RECOVERED"
        }
    ],

When I look up this transaction on explorer... https://mempool.space/tx/f7b6fe0c4958e5ad303dab547143d3a7354d9945950cbe217773f9f487448296
... I can see it has over 1000 confirmations.

Additionally, lightning explorers like amboss.space are not showing that this channel exists in the gossip... so I really think the channel has been successfully closed, and LND might be showing me this in error?

Also, the "blocks_til_maturity": -916, line in the above output seems strange.

I thought maybe this was due to some sort of loss of synchronization between LND and Bitcoind, so I tried restarting LND, but this "pending force close" hasn't gone away....

[kingpalethe]

here is the output of lncli wallet pendingsweeps

aw73:/$ lncli wallet pendingsweeps
{
        "pending_sweeps": [
                {
                        "outpoint": "d1eb9af8dc3d6dd0524fd779c211bd43ad29e784012e500144eb73e773b8bbb6:0",
                        "witness_type": "COMMITMENT_ANCHOR",
                        "amount_sat": 330,
                        "sat_per_vbyte": 68,
                        "broadcast_attempts": 0,
                        "next_broadcast_height": 824415,
                        "requested_sat_per_vbyte": 0,
                        "requested_conf_target": 144,
                        "force": false
                },
                {
                        "outpoint": "cc7a0461db0c042d2d487170308bd4f02c47d8bbf05614830f366a030ce51f21:0",
                        "witness_type": "COMMITMENT_ANCHOR",
                        "amount_sat": 330,
                        "sat_per_vbyte": 68,
                        "broadcast_attempts": 0,
                        "next_broadcast_height": 824415,
                        "requested_sat_per_vbyte": 0,
                        "requested_conf_target": 144,
                        "force": false
                },
                {
                        "outpoint": "f7b6fe0c4958e5ad303dab547143d3a7354d9945950cbe217773f9f487448296:2",
                        "witness_type": "COMMITMENT_TIME_LOCK",
                        "amount_sat": 5490,
                        "sat_per_vbyte": 171,
                        "broadcast_attempts": 0,
                        "next_broadcast_height": 824415,
                        "requested_sat_per_vbyte": 0,
                        "requested_conf_target": 6,
                        "force": false
                }
        ]
}```

[guggero]

The funds are currently in the time locked output and need to be swept, which is the third entry sou see in pendingsweeps. But since it's a relatively small amount and the fees are currently high, it's not economical to do so at the current time and lnd waits.
So you just need to wait for this to resolve.

[bitromortac]

You can see from the transaction on mempool.space that the to_local output hasn't been swept yet (5490 sat ~ $2). Chain fees are still high, so it would cost you more than what you would gain. It is normal that the channel remains in the pending close state until all outputs get resolved, you need to wait for lower onchain fees for the output to get recovered. I'd watch closely if the sweeper claims the output once onchain fees drop.

[microlancer]

So what happens if the chain fees never go down? Is there a way to abandon the sweep?