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
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-create-manage-compute-instance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,7 +166,7 @@ A compute instance is considered inactive if the below conditions are met:
166
166
* No active Jupyter terminal sessions
167
167
* No active AzureML runs or experiments
168
168
* No SSH connections
169
-
* No VS code connections; you must close your VS Code connection to your compute instance to be considered inactive. Sessions are auto-terminated if VS code detects no activity for 3 hours.
169
+
* No VS code connections; you must close your VS Code connection for your compute instance to be considered inactive. Sessions are auto-terminated if VS code detects no activity for 3 hours.
170
170
171
171
Note that activity on custom applications installed on the compute instance is not considered. There are also some basic bounds around inactivity time periods; CI must be inactive for a minimum of 15 mins and a maximum of 3 days.
0 commit comments