Domino shuts down long-running workspaces after a period, as defined by your administrator, to prevent users from starting a workspace and then forgetting to shut it down. Your administrator can also configure workload notifications to define if and when users will receive notifications about long-running workspaces.
|
Note
| These options do not apply to long-running Jobs. Jobs are intended to run to completion without interruption once started. This ensures that production runs execute reliably and that Domino resources are used in the most cost-efficient manner. |
Long-running workspaces that are automatically shut down will auto-commit your work before shutting down. No additional settings are required.
However, keep the following in mind:
-
Linked Git repositories will not be pushed/committed unless you’ve specifically set that up.
-
Only data that has been written to disk will be preserved (that is, any in-memory objects and files not yet saved to disk will be lost). For example, you must save a workspace you’re editing within Jupyter in order for it to be committed when the workspace shuts down.
Change the automatic shutdown period
You can adjust this period to make it shorter. If you make a change, it applies to all workspaces owned by you.
-
Click your account name.
-
Click Account Settings:
-
Click Workspace Settings.
In the Workspace Settings section, you can see the automatic shutdown period defined by your administrator.
-
Select Shutdown my long-running workspaces <n> minutes/hours after startup.
If you leave the checkbox cleared, the time limit configured by your administrator applies.
-
Select a different time limit for long-running workspaces.
The shutdown time is the time since the workspace was started. The workspace shuts down automatically after it has been running for this period.