[Bug] Auto stop feature not working anymore

[avillach]

Describe the bug
in our PROD environment
SageMaker Notebook-v2
configuration: Auto-stop idle-time : 60min

To Reproduce
Steps to reproduce the behavior:
just launch sagemaker, non of them will stop

Expected behavior
it should stop after 60mn
Screenshots

Versions (please complete the following information):

• Release Version installed 3.1.0

Additional context
Add any other context about the problem here.

[nguyen102]

Thanks for filing this bug Paul. Version 3.2 of SWB has a fix for AutoStop not working. I would recommend upgrading SWB to atleast version 3.2 to get this fix.

[avillach]

Hi, I updated SWB to v3.3.0
SageMaker notebooks still don't stop automaticly after 60mn.

Do I need to IMPORT and APPROVE the latest workspace "SageMaker Notebook-v3" to see this bug corrected? If so, this wasn't described in bug report #515 neither in release v3.2.0 that we ALSO had to IMPORT and APPROVE the latest workspace

[avillach]

After updating to Sagemaker v3 the note book now stops automaticly BUT I can't see the status change in SWB UI.
It still shows as AVAILABLE but login in AWS console I can see that it STOPTED.
Thanks
Paul

Screenshot showing the SAME notebook from SWB UI and AWS Console

[jol-ster]

This is likely linked to a status update bug that we have in our backlog. The polling of the status and the resulting update to the DDB table has a possible disconnect. The item is open, and I'll update as we are able to address it. Thank you for the examples.

[avillach]

FYI: since I updated to 3.3.1 I don't see this issue anymore. Stoped SageMaker are now being displayed as STOPED in SWB UI