-
Notifications
You must be signed in to change notification settings - Fork 887
UI shows Stop & Start buttons for workspace in a failed state #7329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is a limitation from the architecture perspective. Since it is in a failed state, it should be able to start or stop. It was an old customer request and since we can't predict the correct state, we should keep both actions. |
I think the jank is that we have a "Try again" without indicating whether that's a start or stop. It's confusing having three actions on the screen and not a clear one to pick. |
Hm... I see, so should we remove the "Start" and "Stop" actions and show a "Try again"? |
Temporarily setting this as blocked while Bruno finishes the XState transition for the Workspace logic |
@Parkreiner Is it unblocked now? |
@mtojek Yeah, now that the last XState refactor has been merged in, I'm aiming to wrap this up today |
version
0.23.0
the user is shown the
Stop
,Start
, andTry again in debug
mode buttons when viewing a workspace in a failed state. this UX is confusing asStop
suggests the workspace is running, whileStart
suggests it's in an off state.this is exacerbated when the template for failed workspace has been updated, adding the "Update" button to the view:
The text was updated successfully, but these errors were encountered: