{"version":"2.1.321","anchor":"auto-mode-rules-get-their-own-unsupported-setting-notice-tl","canonical_anchor":"auto-mode-rules-get-their-own-unsupported-setting-notice-tl","heading":"Auto-mode rules get their own cloud-session notice, and stalled TLS handshakes time out","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-rules-get-their-own-unsupported-setting-notice-tl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Auto-mode rules get their own cloud-session notice, and stalled TLS handshakes time out\n\nCloud sessions report auto-mode rules as their own reason, and a stalled secure connection now stops with `ERR_TLS_HANDSHAKE_STALLED`\n\n**What**\n\n- Auto-mode rules: when a setting that restricts a cloud session is only auto-mode rules, the compatibility message gives a separate `auto_mode_rules` reason with its own text. Before, every restricting setting was reported as a tool restriction.\n\n- Stalled connections: a TLS handshake is the first exchange that sets up a secure connection to a server. If it does not finish in time, HTTPS requests now stop with `ERR_TLS_HANDSHAKE_STALLED` and the message \"The TLS handshake with the server did not finish in the time allowed, normally 120 seconds. Check the network or proxy.\" This error is treated as its own kind of network failure.\n\n**Why**\n\nCloud sessions with auto-mode rules get a more accurate explanation, and a stuck connection gives a clear error pointing to the network or proxy instead of hanging.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}