The behavior only takes effect after you start the workspace again - note that it says "Your workspace will shut down 5 hours after its next start." I agree that it's surprising behavior, but the problem is that you could edit your workspace more than 5 hours after it started, making the instruction technically impossible to follow (though it could shut down immediately, but I don't know if that's ideal either). @bpmct what do you think?

The behavior only takes effect after you start the workspace again

Could we change this behavior to be effective immediately?

the problem is that you could edit your workspace more than 5 hours after it started, making the instruction technically impossible to follow (though it could shut down immediately, but I don't know if that's ideal either).

When a workspace schedule is edited, perhaps we should bump the TTL by 1 hour (and notify the user) to avoid immediate shutdowns. Perhaps this only happens if the calculated shutdown time is less than 1 hour from now. When the user has "activity" on their workspace (VS Code, SSH, websocket on coder_app), we also bump the schedule by one hour so this seems appropriate.

Alternatively, we could change the shutdown to stop at n hours after the workspace is edited, instead of from when it is started.

Potentially unrelated but the whole auto stop is not reflecting entirely for us in 0.12.6: #5146

Stopping and starting makes no difference. Users expect this to reflect on running workspaces if it can be edited on a running workspace anyway.

Really annoying bug.