{"version":"2.1.248","anchor":"fast-path-eligibility-now-records-why-it-declined","canonical_anchor":"fast-path-eligibility-now-records-why-it-declined","heading":"Fast-path eligibility now records why it declined","tier":"internal","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/fast-path-eligibility-now-records-why-it-declined","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Fast-path eligibility now records why it declined\n\nThe fast-path check now records why it declined; the decisions are unchanged.\n\n**What**\n\nThe check that decides whether a request can use the fast gateway path now returns a reason along with its yes\/no answer, so refusals can be reported in diagnostics. The answers themselves are unchanged.\n\n**Details**\n\n- Reasons: `unpinned_gateway`, `third_party_provider`, `custom_base_url`, `sandboxed_entrypoint`, `unsupported_subscription`, `no_auth`.\n\n**Evidence**\n\n`sandboxed_entrypoint`\n\n- Area: Diagnostics\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}