How do i I do a mutual shut of a channel with the next charge on Core Lightning after from the state CLOSINGD_COMPLETE?

I tried to shut one among my channels as we speak by operating:
lightning-cli -k shut id=******* unilateraltimeout=10800 feerange=[1000,4000]
I obtained the next output:

         # Sending closing charge supply 424sat, with vary 151sat-600sat
# Obtained closing charge supply 424sat, with vary 424sat-424sat
{
   "tx": "*******************************************************************************************************************************************************************************",
   "txid": "***************************************************",
   "kind": "mutual"
}

After a few hours the transaction continues to be unconfirmed onchain.
I attempted to shut the identical channel once more with the next charge: lightning-cli -k shut id=******* unilateraltimeout=10800 feerange=[3000,5000] however I obtained this error:

{
   "code": -32602,
   "message": "id: Channel in state CLOSINGD_COMPLETE: invalid token (see logs for particulars)"
}

The log, .lightning/bitcoin/log reveals:

2024-12-15T13:54:28.075Z INFO    lightningd: JSON COMMAND shut: Invalid parameter id (Channel in state CLOSINGD_COMPLETE): token '"******x****x*"'

Under are the channels state adjustments and standing as present by the output of listchannels:

 "state_changes": [
            {
               "timestamp": "2024-08-14T06:27:46.645Z",
               "old_state": "CHANNELD_AWAITING_LOCKIN",
               "new_state": "CHANNELD_NORMAL",
               "cause": "user",
               "message": "Lockin complete"
            },
            {
               "timestamp": "2024-12-15T08:55:13.190Z",
               "old_state": "CHANNELD_NORMAL",
               "new_state": "CHANNELD_SHUTTING_DOWN",
               "cause": "user",
               "message": "User or plugin invoked close command"
            },
            {
               "timestamp": "2024-12-15T08:55:13.552Z",
               "old_state": "CHANNELD_SHUTTING_DOWN",
               "new_state": "CLOSINGD_SIGEXCHANGE",
               "cause": "user",
               "message": "Start closingd"
            },
            {
               "timestamp": "2024-12-15T08:55:13.952Z",
               "old_state": "CLOSINGD_SIGEXCHANGE",
               "new_state": "CLOSINGD_COMPLETE",
               "cause": "user",
               "message": "Closing complete"
            }
         ],
         "standing": [
            "CHANNELD_NORMAL:Reconnected, and reestablished.",
            "CLOSINGD_SIGEXCHANGE:We agreed on a closing fee of 424 satoshi for tx:***********************************************************"
         ],

What might I do to unravel this subject? Can the state CLOSINGD_COMPLETE of the channel change to a brand new state that may enable me to try to shut the channel with the next charge?