- Notifications
You must be signed in to change notification settings - Fork917
docs: clarify workspace scheduling priority and autostop requirement behavior#18447
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
Open
blink-so wants to merge3 commits intomainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
+43 −0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
…behavior- Add priority section to template schedule docs explaining how autostop requirements take precedence over user settings- Add note to user guide about autostop requirement overrides- Add FAQ section addressing common scheduling confusion- Include specific scenarios showing when requirements vs user settings applyFixes confusion around when workspaces shut down when both template autostop requirements and user autostop settings are configured.Co-authored-by: matifali <10648092+matifali@users.noreply.github.com>
@stirby Could you please review this PR? This addresses the scheduling priority confusion that was discussed in Slack, specifically clarifying how autostop requirements interact with user-configured autostop settings. The documentation now clearly explains that:
This should help reduce customer confusion about when workspaces will actually shut down. |
Fixes lint failure by removing trailing whitespace that was causing the CI check to fail.Co-authored-by: matifali <10648092+matifali@users.noreply.github.com>
The markdown linter expects blank lines after scenario headings before list items.This fixes the CI lint failure by conforming to the expected markdown format.Co-authored-by: matifali <10648092+matifali@users.noreply.github.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves documentation clarity around workspace scheduling priority, specifically addressing confusion about how autostop requirements interact with user-configured autostop settings.
Changes
Template Admin Documentation (
docs/admin/templates/managing-templates/schedule.md)User Guide Documentation (
docs/user-guides/workspace-scheduling.md)Problem Solved
Users were confused about scheduling behavior in scenarios like:
Result: Workspace still shuts down daily during quiet hours (requirement takes precedence)
Testing
/coderd/schedule/autostop.goAddresses user confusion reported in Slack about scheduling priority behavior.