{"version":"2.1.222","anchor":"connectivity-check-rewritten-on-fetch-with-a-timeout-and-pro","canonical_anchor":"connectivity-check-rewritten-on-fetch-with-a-timeout-and-pro","heading":"Connectivity check rewritten on fetch, with a timeout and proxy awareness","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/connectivity-check-rewritten-on-fetch-with-a-timeout-and-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Connectivity check rewritten on fetch, with a timeout and proxy awareness\n\nConnection checks now time out properly and record whether your proxy was used.\n\n**What**\n\nThe hello-endpoint probe used by the connection diagnostics now runs on fetch with an explicit timeout and reports whether a proxy was involved.\n\n**Details**\n\n- Uses `AbortSignal.timeout` rather than the previous HTTP client, and cancels the response body.\n- A timed-out probe is reported as a distinct error rather than a generic failure.\n- The result records `usedProxy` so the failure UI can tell whether a configured proxy was actually in play.\n\n**Evidence**\n\n`usedProxy`\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}