You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user sets an inactivityTTL in the template schedule page and there are already inactive workspaces that will be immediately scheduled to be deleted, we should inform the user and allow them to take action via a modal, e.g.
30 workspaces already match this filter. These workspaces will be scheduled for deletion in 14 days.
[Confirm] | [Cancel]
"Confirm" would go ahead and set the inactivityTTL, "Cancel" would cancel the action altogether. It would fall upon the user to do something about those 30 workspaces prior to going back and attempting to reset the inactivityTTL.
The text was updated successfully, but these errors were encountered:
Down the road, we should figure out a good way for the user to more easily identify those 30 workspaces. ATM the workflow would be filtering on inactive workspaces in the /workspaces page. Consider adding a link to this filter from within the modal.
When a user sets an
inactivityTTL
in the template schedule page and there are already inactive workspaces that will be immediately scheduled to be deleted, we should inform the user and allow them to take action via a modal, e.g.30 workspaces already match this filter. These workspaces will be scheduled for deletion in 14 days.
[Confirm] | [Cancel]
"Confirm" would go ahead and set the
inactivityTTL
, "Cancel" would cancel the action altogether. It would fall upon the user to do something about those 30 workspaces prior to going back and attempting to reset theinactivityTTL
.The text was updated successfully, but these errors were encountered: