Sent money to loop address by mistake

[valiantgroves-design]

Good day,
Asking for help, made a mistake and sent money to loop address
I made a loop request for ‎0.18850000 but accidentally instead of using my address for forward I paste loop address money comes from
txid: 4d1dec0bea417ab85ada8708d0e27cf829a27cda8e93a22256bdbdaeb96286bd

address I used by mistake:
bc1pwyya7h0n3qg7e4u05tjuurudxkgxx77l9z2fvhkxscanf59s3phsmt4f9e

correct address for return: bc1q626kdqhhquwx3lmrr08kc3laau949pn7zlxx34

swap info:
{
"amt": "18850000",
"id": "4cc3d97e082a9fd8ae26dd02e7d07389f5281d1ef9d21896b120e1a6cf66d402",
"id_bytes": "4cc3d97e082a9fd8ae26dd02e7d07389f5281d1ef9d21896b120e1a6cf66d402",
"type": "LOOP_OUT",
"state": "SUCCESS",
"failure_reason": "FAILURE_REASON_NONE",
"initiation_time": "1766197797497793774",
"last_update_time": "1766199935181746901",
"htlc_address": "bc1palxgh8xsj5ejlg8hlzv0jau7lh4wanx4mrf0ecy5esswlunn2z5qal77u9",
"htlc_address_p2wsh": "",
"htlc_address_p2tr": "bc1palxgh8xsj5ejlg8hlzv0jau7lh4wanx4mrf0ecy5esswlunn2z5qal77u9",
"cost_server": "18897",
"cost_onchain": "113",
"cost_offchain": "60380",
"last_hop": "",
"outgoing_chan_set": [
"1019032874277404672"
],
"label": "",
"asset_info": null
},

[alexbosworth]

can you put what version of loop you were using?

[valiantgroves-design]

@alexbosworth

VERSION:
0.31.2-beta commit=v0.31.2-beta commit_hash=

[alexbosworth]

ok yeah aside from the resolution of this, it may be more of an issue on the older versions, please make sure to keep your loop daemon updated

[alexbosworth]

After you updated what does your version show now?

[valiantgroves-design]

@alexbosworth
sorry, I'm unable to update it at the moment. There is no resolution for me without update?

[alexbosworth]

We're looking into it, but is there a problem with the updating process?

[valiantgroves-design]

@alexbosworth
just don't have full access to the servers console at the moment, would do it tomorrow

[alexbosworth]

OK let me know when you can update, I don't think we can resolve this anyway at the moment because it's not a supported mode and it's the weekend but we are working on some ways to address this more easily and more automatically

[valiantgroves-design]

@alexbosworth
node has been updated

"version": "0.31.5-beta",
"network": "mainnet",

[alexbosworth]

Great we are working on a fix now for this issue, but this new version also already has mitigations to reduce the possibility of the error happening in the first place

[alexbosworth]

Looking at this we think there will be a need for a new update to Loop to correct this issue, but we are prioritizing this change