Title: Explain why workspace is kept alive · Issue #17320 · coder/coder · GitHub
Open Graph Title: Explain why workspace is kept alive · Issue #17320 · coder/coder
X Title: Explain why workspace is kept alive · Issue #17320 · coder/coder
Description: Problem Statement Many users have reported frustration with workspaces not automatically shutting down as expected with their autostop configuration. The TTL of these workspaces is extended by our activity bump feature, which postpones t...
Open Graph Description: Problem Statement Many users have reported frustration with workspaces not automatically shutting down as expected with their autostop configuration. The TTL of these workspaces is extended by our ...
X Description: Problem Statement Many users have reported frustration with workspaces not automatically shutting down as expected with their autostop configuration. The TTL of these workspaces is extended by our ...
Opengraph URL: https://github.com/coder/coder/issues/17320
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Explain why workspace is kept alive","articleBody":"## Problem Statement\nMany users have reported frustration with workspaces not automatically shutting down as expected with their autostop configuration. The TTL of these workspaces is extended by our activity bump feature, which postpones the shutdown when a user is \"active\" in a workspace. \n\nHowever, [the definition of activity](https://coder.com/docs/user-guides/workspace-scheduling#activity-detection) can be a bit convoluted, and consequently, the activity bump behavior is unpredictable. Administrators want to diagnose exactly _why_ a workspace is being kept alive when seemingly no connections are active. Then, the administrator can hunt down the connection and close it or roll out a permanent solution.\n\nA solution should help administrators understand:\n- When the last time a workspace's TTL was bumped\n- The type of connection that incremented it\n- The source of that connection (some client ID possibly?)\n\n> [!NOTE]\n> We implemented this previously with a `connected` pill in the workspace dashboard. However, because viewing a workspace in the dashboard counted as activity, this was practically always active. Additionally, it did not sufficiently inform users on where the connection was coming from. \n\n### A proposal\n\nA user suggested logging the events or the last event that bumped activity on the workspace page. Something simple like a schedule tooltip that shows:\n\n```\nActivity detected from \u003csource> \u003ctime> ago. \n```\n\n```\nActivity detected from webterminal 15 minutes ago. \n```\n\n```\nActivity detected from SSH 46 minutes ago. \n```","author":{"url":"https://github.com/stirby","@type":"Person","name":"stirby"},"datePublished":"2025-04-09T19:28:54Z","url":"https://github.com/coder/coder/issues/17320"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:22abc770-31f2-df00-5466-26546e035d12 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B008:16AB79:1AAE3DE:21EA486:6B014F2D |
| html-safe-nonce | eb6eb5012e3542fcd94cc72866690e5da930612c0a499fd5c192383175f3c2cc |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMDA4OjE2QUI3OToxQUFFM0RFOjIxRUE0ODY6NkIwMTRGMkQiLCJ2aXNpdG9yX2lkIjoiNjYxMDM2MDY0NzgyNzkzNTAyMSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | e5185f7209513de9dde585969f71e046b4610c614a40b47b0004a16b360b869a |
| hovercard-subject-tag | issue:2983718687 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/coder/coder/17320/issue_layout |
| twitter:image | https://opengraph.githubassets.com/1842c9cbad06ca5f4b5071a7c5edb8b5ec3ec864af13cddf0032a6316f810a67/coder/coder/issues/17320 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/1842c9cbad06ca5f4b5071a7c5edb8b5ec3ec864af13cddf0032a6316f810a67/coder/coder/issues/17320 |
| og:image:alt | Problem Statement Many users have reported frustration with workspaces not automatically shutting down as expected with their autostop configuration. The TTL of these workspaces is extended by our ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | stirby |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/coder/coder git https://github.com/coder/coder.git |
| octolytics-dimension-user_id | 95932066 |
| octolytics-dimension-user_login | coder |
| octolytics-dimension-repository_id | 440752086 |
| octolytics-dimension-repository_nwo | coder/coder |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 440752086 |
| octolytics-dimension-repository_network_root_nwo | coder/coder |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width