Deepnote is designed to support most data analysis workflows, many of which include long-running tasks. This page explains when your projects can be descheduled.
All projects get descheduled when no one is using them. We do this to keep you from using up your free hardware hours unnecessarily. The following three conditions of inactivity have to be met:
The project has no user sessions - this means that you do not have Deepnote open in your web browser.
The project has no running computation - this means that there is no notebook currently executing code
There were no changes to the code or any execution for at least 15 minutes (customizable).
Furthermore, projects running on free hardware get automatically descheduled after running continuously for 24 hours. Any running computation is interrupted. In extraordinary circumstances, we also reserve the right to deschedule the project earlier. In this case, you will see a message "Your hardware was shutdown" next time you visit the project. Please note this does not apply to paid hardware – projects running on paid hardware can run as long as the owner wants.
Finally, projects running on free hardware are descheduled if their owner runs out of free quota and they don't have a paying method set up. In this case, an info message will also appear next time you visit the notebook, notifying you about running out of the free quota.
Users using our pay-per-use hardware can customize the behavior above and prevent the machine being automatically turned off (descheduled) after 15 minutes of inactivity. This can be useful if you're unsure when your long-running job finishes and want to keep its state preserved (such as python variables or terminal outputs). You can currently set the grace period to be either 15 minutes or 24 hours.