If the connection fails (information entry mistake) or stalls (says it connects, but then circles forever "connecting" in the device area), there is no way to retry. Everything is entirely stuck without a way to abort or retry. Even end-tasking as many processes as can be found does not fix the problem. The program remains in a locked state until the entire computer is rebooted. This is a large issue, as rebooting may not always be trivial or even possible to do. The program needs to be able to abort and retry or retry in place or at least have a way to force a full kill without touching the rest of the system; it must not irrecoverably softlock.
I haven't experienced this. No data is being stored that should be persistent through a reboot, so I'm inclined to say that this is something with your setup.
If the connection fails (information entry mistake) or stalls (says it connects, but then circles forever "connecting" in the device area), there is no way to retry. Everything is entirely stuck without a way to abort or retry. Even end-tasking as many processes as can be found does not fix the problem. The program remains in a locked state until the entire computer is rebooted. This is a large issue, as rebooting may not always be trivial or even possible to do. The program needs to be able to abort and retry or retry in place or at least have a way to force a full kill without touching the rest of the system; it must not irrecoverably softlock.