Yes I am bringing this up again. this needs to be matured. this weekend we had to get into a device to troubleshoot. We needed to do a second connection but didn't need to log but you can only do the first two options as cancel drops the connection. I have asked to have cancel to just NOT log the session. This question is about logging. Logging cannot only apply to one session to the same file.

3e1f4635-bad1-4612-b852-3eb581222977.png
1c5ae80e-866e-42ee-ab0a-5f87971f339a.png
Hello,
I've linked your thread to our opened internal ticket, and I will check with the dev team if we can raise the priority on this.
Regards,
Hubert Mireault
Hello,
I've made the change and you can expect it to be available starting with version 2026.2.18.0. The window will look like this, with the "cancel" button instead being "proceed without logs".
I hope that with this change the workflow is more what you'd expect. Please let me know if you have any additional feedback once you're able to try this version.
Regards,
Hubert Mireault
dae89d71-87d2-4773-bd8f-bb1c74236f85.png
that is great! I can still connect to a second instance without logging or any session with the option to log or not but still connect.