Commite0b1536

authored

chore: clarify autostop behaviour for existing workspaces (#20295)

[We have tests to ensure thisbehaviour](https://github.com/coder/coder/blob/152103bf788dc5a4c06586302a255a212e0fe77d/coderd/workspaces_test.go#L2957-L3004),but it is not clearly documented. This PR adds a note clarifyingautostop must be enabled on the template prior to a workspace beingcreated for it to apply to the workspace, i.e. it is not re-read if aworkspace is restarted / stopped and started. This behaviour was raisedby a customer.https://coder.com/docs/user-guides/workspace-scheduling#autostop

1 parent8ac5453 commite0b1536Copy full SHA for e0b1536

File tree

-0

lines changed

-0

lines changed

Lines changed: 3 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -39,6 +39,9 @@ workspace if you're still using it. It will wait for the user to become inactive`
`39`	`39`	`before checking connections again (1 hour by default). Template admins can`
`40`	`40`	`modify this duration with theactivity bump template setting.`
`41`	`41`
	`42`	`+>[!NOTE]`
	`43`	`+>Autostop must be enabled on the template prior to workspace creation, it is not applied to existing running workspaces.`
	`44`	`+`
`42`	`45`	`![Autostop UI](../images/workspaces/autostop.png)`
`43`	`46`
`44`	`47`	`##Activity detection`

Comments

(0)