{"version":"2.1.242","anchor":"bigquery-export-host-check-runs-ahead-of-the-org-setting-che","canonical_anchor":"bigquery-export-host-check-runs-ahead-of-the-org-setting-che","heading":"BigQuery export host check runs ahead of the org-setting check","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/bigquery-export-host-check-runs-ahead-of-the-org-setting-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### BigQuery export host check runs ahead of the org-setting check\n\nThe BigQuery host check runs before the org setting, and a missing dispatch value blocks export entirely.\n\n**What**\n\nThe new host comparison happens before the organisation setting is consulted. When workload-identity dispatch is active, the dispatch host (defaulting to `api.anthropic.com` when unset) is compared with the metrics endpoint host; a mismatch reports success without exporting anything, and a missing dispatch value also blocks the export. When that dispatch path is not active the check passes through.\n\n**Evidence**\n\n`BigQuery metrics export: WIF dispatch host differs from the metrics endpoint host, skipping`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}