Force closed channel with 300+ blocks confirmed closing TX is still in pending

[microlancer]

Is this pending channel still waiting for something? The closing TX is already confirmed:

https://mempool.space/tx/970cf347b1c354730a3ea5c6028541aece0fc2b99c6323280d03dddabb392a87

Should I be doing something or will it clear out from "pending" on it's own? Maybe it's waiting for the sweeper to collect some small amount but the mempool fees are too high to be worth it?

    "pending_force_closing_channels":  [
        {
            "channel":  {
                "remote_node_pub":  "021fa607f2b6ceebe5742aaa7650cf817351e7d70cf47595a48ffd2e5741076b06",
                "channel_point":  "5cde0f17ed6081826ab65dd7f4dda194d90313428b2323c2294a03a925ddccb1:1",
                "capacity":  "1100000",
                "local_balance":  "1079010",
                "remote_balance":  "11756",
                "local_chan_reserve_sat":  "0",
                "remote_chan_reserve_sat":  "0",
                "initiator":  "INITIATOR_REMOTE",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "",
                "private":  false,
                "memo":  ""
            },
            "closing_txid":  "970cf347b1c354730a3ea5c6028541aece0fc2b99c6323280d03dddabb392a87",
            "limbo_balance":  "5000",
            "maturity_height":  0,
            "blocks_til_maturity":  0,
            "recovered_balance":  "330",
            "pending_htlcs":  [
                {
                    "incoming":  false,
                    "amount":  "5000",
                    "outpoint":  "b23b4839cc4085e31e89a07ac151d9b6d06c649f59353c37184be81d544e416e:0",
                    "maturity_height":  821879,
                    "blocks_til_maturity":  -385,
                    "stage":  2
                }
            ],
            "anchor":  "RECOVERED"
        }
    ],

[bitromortac]

Yes, it's still waiting to sweep the 5k sat output here: https://mempool.space/tx/af08060c412d6d3c27db6fe62a95488a3772bab6ffbdb8cfabc00898167cc003, which should be done when onchain fees are lower.