Deepnote is designed to support most data analysis workflows, many of which include running long running tasks. As such, Deepnote does not interrupt your running kernels.
More specifically, all of the following needs to be true for us to deschedule a user project:
It has no user sessions - this means that you do not have Deepnote open and focused in your web-browser.
It has no running running computation - this means that there is no notebook currently executing code
There were no changes to the code for at least 15 minutes.
There are some exceptions to the rules above described in fair usage policy. After the notebook is de-scheduled, we still store the outputs of cells, but the variable states are gone.