I don't think we should do a lock stage, but maybe just present a warning to the user that they are X days away from this workspace being deleted + some button to extend it. I think this would be a good fit for an enterprise feature to help control static costs.

I don't think we should do a lock stage, but maybe just present a warning to the user that they are X days away from this workspace being deleted + some button to extend it. I think this would be a good fit for an enterprise feature to help control static costs.

The lock feature comes from #4501, which we should be able to cheaply reuse here. A banner is necessary in any world too.

Related #5265

Also: lock is unnecessary for MVP.

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

Responding to the stale bot, we would still love to have this feature as we're currently manually monitoring unused workspaces and reaching out to their owners to ask if we can reap them. 🙏

Per #5815 I just want an option to stop on fail so it kills the resources and also allows users to review the logs to see that it stopped because of XYZ reason. Doing too much bottom cleaning right now.

If there was also a scheduled cleanup stopped workspaces that would be a bonus.

@bpmct May be we can do something like https://cast.ai/

Is this related to: #5815 (comment)

And is this actually only going to be an Enterprise feature?

@dcarrion87 — as the feature is primarily to address scale needs and outside of the developer experience, it's planned for enterprise.

Docs on the new feature here: https://coder.com/docs/v2/latest/templates/schedule#failure-cleanup.