Colab Runtime Idle-Detection and Background Execution Limits

Session Persistence and Idle Heuristics

Google Colab employs dynamic resource allocation and session lifetime limits to manage VM availability. While the platform allows for long-running cells, the runtime is subject to an idle-detection heuristic that can trigger a disconnection even while a cell is actively executing code in the background.

The documentation specifies that sessions are ephemeral and subject to timeouts, but it does not define the specific user interactions or system signals required to reset the idle timer. This creates uncertainty when running long-term training loops or data processing tasks that do not produce frequent output or require manual input.

Technical Constraints

• Lack of a documented API or configuration to explicitly signal "activity" to the backend.
• Variable timeout windows based on account tier and current system demand.
• Automatic VM recycling upon session expiration, leading to the loss of all local disk state.

What specific activity types are recognized by the Colab backend to prevent an idle timeout during background cell execution? Is there a documented method to maintain session persistence without simulating user interface interaction?