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 an admin sets Default TTL to 0 (disabling autostop), the Activity Bump field remains editable in the template scheduling UI. This is confusing and dangerous because:
Activity Bump has no effect when there's no deadline to extend
Admins may set both Default TTL=0 and Activity Bump=0 thinking they're "fully disabling" autostop
Key Insight: Activity Bump is a Self-Healing Mechanism
When activity_bump > 0 and default_ttl=0, activity bumps actually clear the deadline on running workspaces. This is a safety mechanism - the bump logic applies the new TTL (0) which results in deadline=null.
But when admins set bothactivity_bump=0 AND default_ttl=0:
No bumps occur to "heal" the workspace
Existing deadline persists
Workspace autostops when the old deadline passes
Proposed Solution
When Default TTL is set to 0:
Disable or hide the Activity Bump field
Show a tooltip or helper text: "Activity bump only applies when a default TTL is configured. Leaving activity bump enabled allows running workspaces to clear their existing deadlines."
Alternatively, if Default TTL is set to 0, automatically set Activity Bump to a sensible default (e.g., 1 hour) rather than allowing 0.
Why This Helps
This is a minimally invasive way to reduce the chances of admins changing Activity Bump to 0 at the same time they disable autostop. By preserving activity_bump > 0, the self-healing mechanism remains active and running workspaces will naturally clear their deadlines on the next activity bump cycle.
It doesn't fully solve the underlying issue of existing workspaces retaining their deadlines (#21688), but it removes a common footgun from the UI and preserves the safety mechanism.
Problem
When an admin sets
Default TTLto 0 (disabling autostop), theActivity Bumpfield remains editable in the template scheduling UI. This is confusing and dangerous because:Activity Bumphas no effect when there's no deadline to extendDefault TTL=0andActivity Bump=0thinking they're "fully disabling" autostopKey Insight: Activity Bump is a Self-Healing Mechanism
When
activity_bump > 0anddefault_ttl=0, activity bumps actually clear the deadline on running workspaces. This is a safety mechanism - the bump logic applies the new TTL (0) which results indeadline=null.But when admins set both
activity_bump=0ANDdefault_ttl=0:Proposed Solution
When
Default TTLis set to 0:Activity BumpfieldAlternatively, if
Default TTLis set to 0, automatically setActivity Bumpto a sensible default (e.g., 1 hour) rather than allowing 0.Why This Helps
This is a minimally invasive way to reduce the chances of admins changing
Activity Bumpto 0 at the same time they disable autostop. By preservingactivity_bump > 0, the self-healing mechanism remains active and running workspaces will naturally clear their deadlines on the next activity bump cycle.It doesn't fully solve the underlying issue of existing workspaces retaining their deadlines (#21688), but it removes a common footgun from the UI and preserves the safety mechanism.
Related Issues
Created on behalf of @bjornrobertsson