Hi @Dick_Cooper —— Thank you for the following up with us. The additional insight is appreciated!
As you know, we were able to reproduce some issues during our field testing and were able to make some fixes which we rolled out with B334. So far, initial reports are that things are much more stable for the vast majority of users we’ve spoken with, which of course is great news.
From what I can tell, things have been more stable for you since the release, but you’re also still seeing some instability. This suggests that you may have actually been experiencing multiple issues – the problems we appear to have resolved in our last release, and something else that’s distinct from what others have been experiencing. Most likely, something about your environment is different, and if we’re going to get things stable for you we’ll need to identify what that is.
The support team is ready to help narrow down what may be causing this to occur in your setup, but I want to be clear up front that this will require more in-depth troubleshooting – in cases like this, the only way forward is to rule out factors one-by-one, which can take time and effort.
This kind of troubleshooting almost always works if we’re methodical, but I know you’ve been frustrated by this process in the past, and so I want to be clear to you that this isn’t likely to be something we’re going to resolve by looking at logs or releasing bug fixes. We’ll need to do some testing in your environment related to your Core, your wifi, your network hardware, the audio devices, and so on.
If you want to proceed, we’ll work up a test plan with our QA department. Conversely, as Mike mentioned, we’d be happy to process a refund if you’re not interested in continuing to investigate this.
We’re confident we can identify the problem here, but some issues are more complex than others, and we want to be clear with you about your options going forward. We really appreciate your patience, and please let us know how you’d like to proceed, or if you have any questions. Thanks Dick!
-Eric