Technical problem with trying to unstake EOS so it can be withdrawn to an exchange etc

As I understand it, in order to transfer/withdraw/exchange EOS, it must first be unstaked, after which it is held for 3 days temporarily in the ‘net’ status column, and is then automatically transferred to the EOS category.

If the way this is supposed to work, then can someone please explain why after I undelegated some EOS several weeks ago, it is still sitting in the “net” field and never moved automatically to the EOS field after 3 days had passed? Is there another step I have to make to make it transfer if it doesn’t happen automatically? It has been stuck in the “NET” (3 day pending) category for something like 2 or 3 months now. Is there also a reason why this process must be done via eostoolkit.io and cannot simply be done via scatter?

Oh and I tried the refund fallback option as well, and got a failure message with this data…

{ “code”: 500, “message”: “Internal Service Error”, “error”: { “code”:
3050003, “name”: “eosio_assert_message_exception”, “what”:
“eosio_assert_message assertion failure”, “details”: [ { “message”:
“assertion failure with message: refund request not found”, “file”:
“wasm_interface.cpp”, “line_number”: 924, “method”: “eosio_assert” },
{ “message”: “pending console output: “, “file”: “apply_context.cpp”,
“line_number”: 72, “method”: “exec_one” } ] } }

Thank You

p.s It is wonderful that you allow people to post without having to open an account, thus removing one of the most irritating, exasperating, and oppressive barriers to free and open discussion on the internet. This feels like the exact kind of spirit we should have around open blockchain projects. Well done!