{"version":"2.1.318","anchor":"insights-query-opts-into-sendsidequerybeta","canonical_anchor":"insights-query-opts-into-sendsidequerybeta","heading":"Insights requests opt into sendSideQueryBeta","tier":"internal","area":"Insights","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/insights-query-opts-into-sendsidequerybeta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Insights requests opt into sendSideQueryBeta\n\nThe \/insights model request, including its facet extraction, now sets sendSideQueryBeta, and the insights run uses a new running-flag mechanism\n\n**What**\n\nThe request that `\/insights` sends to the model now sets `sendSideQueryBeta: true`, alongside `querySource: \"insights\"`. A side query is a separate, smaller model request made in the background, apart from the main conversation.\n\n- The insights facet extraction side query sets `sendSideQueryBeta`.\n\n- Another part of the code treats a request as eligible for some beta handling when its `querySource` is in a fixed list or when `sendSideQueryBeta` is true. Insights requests now meet that condition. The members did not trace what that handling is.\n\n- Other call sites set the same option.\n\n- The insights run now uses a new mechanism that tracks whether it is currently running.\n\n**Why**\n\nIn practice, `\/insights` requests may now be sent differently, for example with a beta header or along a different request path. A beta header is an extra label on a request that switches on features still being tested. If insights results or failures change after this release, this is a likely place to look.\n\n- Area: Insights\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}