NotificationsYou must be signed in to change notification settings
Fork1.1k
Star11.4k

chore: clarify autostop behaviour for existing workspaces#20295

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

rowansmithau merged 1 commit intomainfromzd4447

Oct 15, 2025

Merged

chore: clarify autostop behaviour for existing workspaces#20295

rowansmithau merged 1 commit intomainfromzd4447

Oct 15, 2025

Conversation

Copy link

Contributor

rowansmithau commentedOct 14, 2025•
edited
Loading

We have tests to ensure this behaviour, but it is not clearly documented. This PR adds a note clarifying autostop must be enabled on the template prior to a workspace being created for it to apply to the workspace, i.e. it is not re-read if a workspace is restarted / stopped and started. This behaviour was raised by a customer.

https://coder.com/docs/user-guides/workspace-scheduling#autostop

chore: Clarify autostop behaviour for existing workspaces

f9c4949

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