It seems to be fixed now with the latest Chrome extension. Thanks for the help, and great to see the quick turnaround on fixing the issue. As noted in my last post, you may have to set the timeout back to “Never” manually again after you re-install the new version of the Extension. After that it should stay that way and the issue should be fixed.