Closed eburtness closed 2 years ago
May be a duplicate of #164 and #158
This issue has been linked to a new work item: W-11492790
Hi @eburtness - Thanks for trying out Code Builder and giving us feedback. Behind the scenes, we have some checks to try to detect when you are idle. When you close a tab or go idle, the session time should be within about 15-30 minutes of the rough time. We capped the hours per month for beta so that we could offer an open beta for anyone to try. Do you still have time remaining this month?
Hi @smaddox-sf, thanks for looking into this. Yes, I still have time remaining. If the cap is only for the beta then I think this is not a problem and I was just overly worried at seeing my time run down. :)
I haven't seen it run for more than 30 minutes after I closed the tab, so it sounds like that is the expected behavior and we're fine! Feel free to close the issue. Thanks!
Hi @smaddox-sf I wonder if this issue is still ongoing? I have closed the tab (according instruction here) but still the time-remaining counter is running. The test Code Builder got wiped out in 20h regardless the tab is closed.
Description After closing the Code Builder tab, usage time continues to be counted for an additional 20-30 minutes. How can I stop the clock when I'm done using it?
To Reproduce
Expected behavior Hours Remaining to stay constant when no Code Builder tabs are open
Screenshots
Desktop (please complete the following information):
Additional context Overview doc says "We highly recommend that you save your work and close the browser tab that is running Code Builder to stop the usage clock when you aren’t using Code Builder." This sounds like all you have to do is close the tab to stop the clock.