Merge pull request #43 from durgasury/update-readme

update readme

Author: durgasury

README.md

@@ -19,6 +19,7 @@ You can either install the extension manually, or automate the install through S
 You can create and attach a Lifecycle configuration script to the default JupyterServer app for your users. The LCC script is available [here](https://github.com/aws-samples/sagemaker-studio-lifecycle-config-examples/tree/main/scripts/install-autoshutdown-server-extension). For instructions to create and attach LCCs, and setting defaults, see [Use Lifecycle Configurations with Amazon SageMaker Studio](https://docs.aws.amazon.com/sagemaker/latest/dg/studio-lcc.html). For detailed setup instructions, see [Customize Amazon SageMaker Studio using Lifecycle Configurations](https://aws.amazon.com/blogs/machine-learning/customize-amazon-sagemaker-studio-using-lifecycle-configurations/). Once the LCC is set as a default at the domain level, all users inherit the extension by default. 
 
 > :warning:
+>- If you are installing other JL3 extensions, code-server etc. on your LCC script, ensure that the auto shutdown plugin is the last step in your LCC. Specifically, the `set-time-interval.sh` file should be executed at the last line of your script. Without it, you risk the chance of having the plugin installed, but not polling for idle kernels.
 >- If you are switching Studio to JupyterLab3, and you have previously installed the plugin through LCC, you need to update the LCC to work with JupyterLab3. Pull the script from Github [here](https://github.com/aws-samples/sagemaker-studio-lifecycle-config-examples/tree/main/scripts/install-autoshutdown-server-extension) and recreate the LCC. 
 >- If you have existing user profiles in your domain, they will have to restart their "default" JupyterServer app to inherit the LCC configuration.