Ir al contenido principal

Remote Connection Timeouts

Actualizado hoy

Introducción

If your Terminal, Remote Control, or Process Explorer session drops when you switch browser tabs or leave it idle, the cause is almost always the browser throttling background activity — not a problem with your device or Level workspace. Chromium-based browsers (Chrome, Edge) aggressively limit network connections in inactive tabs to save memory and power.


Remote Connection Timeouts

Add Level to Chrome's Always-Active List

This is the recommended fix. It keeps Level's sessions alive without disabling Memory Saver globally.

  1. In Chrome or Edge, navigate to chrome://settings/performance.

  2. Find the Memory Saver section.

  3. Next to "Always keep these sites active", click Add.

  4. Enter your Level workspace URL (e.g., app.level.io).

  5. Click Add.

Chrome Setting

💡 TIP: If your team uses a custom Level domain, add that URL instead of (or in addition to) app.level.io.


Disable Memory Saver and Energy Saver

If you'd rather turn these features off entirely, both settings are on the same page at chrome://settings/performance.

  • Memory Saver — Suspend inactive tabs to free RAM. Turning this off keeps all tabs fully active at the cost of higher memory usage.

  • Energy Saver — Reduces background activity when on battery or when the battery is low. Turning this off prevents it from interrupting live sessions.

⚠️ WARNING: Disabling Memory Saver increases RAM usage, which can affect performance on devices with limited memory. The always-active list approach above is preferable if global Memory Saver is otherwise working for you.

ℹ️ NOTE: These settings apply to Chromium-based browsers (Chrome, Edge, Brave, etc.). Firefox and Safari have equivalent tab suspension features under different settings menus — check your browser's performance or privacy settings.


If Sessions Are Still Disconnecting

Browser throttling accounts for most timeout issues, but not all. If you've made the changes above and sessions still drop:

  • Disconnects immediately when connecting — likely a connectivity issue, not browser throttling. See Relay/P2P Troubleshooting.

  • Disconnects while the tab is active and visible — not a browser issue. Contact support.

  • Disconnects happen across multiple browsers — also likely a connectivity issue rather than browser settings.

When contacting support, include your browser name and version, OS, and a description of what you were doing when the session dropped.


Preguntas frecuentes

  • Does this affect Terminal, Remote Control, and Process Explorer equally? Yes. All three rely on a continuous live connection through the browser. Any browser throttling that interrupts network activity will affect all of them the same way.

  • I added Level to the always-active list but sessions are still dropping. Check whether Energy Saver is also enabled at chrome://settings/performance — it can limit background activity independently of Memory Saver. If both are configured and sessions still drop, the issue is likely connectivity rather than browser settings. See Relay/P2P Troubleshooting.

  • Does this only affect Chrome? Primarily. Chrome and Chromium-based browsers (Edge, Brave) are the most aggressive about background tab throttling. Firefox and Safari have similar features but typically less aggressive defaults. If you're seeing this in a non-Chrome browser, check that browser's performance or tab management settings.

  • Can I use a browser extension instead of changing these settings? Some extensions claim to prevent tab suspension. They're generally less reliable than the native always-active list and may introduce other issues. The native setting is the better option.

¿Ha quedado contestada tu pregunta?