Skip to content

Commit ea2366a

Browse files
shouryajteochaban
andauthored
Update articles/machine-learning/how-to-create-manage-compute-instance.md
Co-authored-by: teochaban <[email protected]>
1 parent 0e1a0b8 commit ea2366a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/how-to-create-manage-compute-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ A compute instance is considered inactive if the below conditions are met:
166166
* No active Jupyter terminal sessions
167167
* No active AzureML runs or experiments
168168
* 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.
170170

171171
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.
172172

0 commit comments

Comments
 (0)