Since Monday Aug 1 through today we have continually observed:
- Workspaces fail to start.
- Workspaces fail to stop.
- Workspaces crash when stopped (last backup failed: workspace does not exist).
- Workspaces crash when they time out.
These events postdate all similar allegedly fixed problems I’ve seen in the forum. We have some documentation, but won’t post it here, as you’ve certainly seen it all before. I’m in Portland, Oregon on a gigabit fiber Internet connection with no known outages during this period. We’ve had little trouble with running workspaces.
Sometimes when a workspace fails to start, or crashes, it can later be located in the workspace list. Sometimes it can be restarted from there, other times not. Generally speaking we don’t trust phantom or crashed workspaces. We delete them and start over.
We have lost data. We are not interested in salvaging any workspaces at this time, however. We have learned to push early and often–and always before stopping a workspace, or getting up from a chair.
We would like to know if you intend to fix these problems. This is very frustrating for us, and my team’s patience is starting to wear a little thin. They’re developers, too, and they know very well that I will come after them if they introduce instability into a previously stable product, regardless of whatever other magic they’re currently performing. I’m trying to get us off desktops, but I can’t do that if you can’t provide reasonably stable cloud environment. We are not doing anything clever (no custom Docker images). Please let us know what to expect.
Senior Software Architect
QIS Project Inc.