Not Routable Queries
Some BigQuery jobs can't be routed through Yuki, so Yuki can't optimize them. They still count toward your total BigQuery spend, and Yuki shows them separately as Not Routable.
Not Routable vs. Not Routed Through Yuki
Yuki splits your BigQuery spend into three groups:
| Group | What it means |
|---|---|
| Routed Through Yuki | Queries that went through the Yuki Proxy and were optimized. |
| Not Routed Through Yuki | Queries that Yuki could route but that connected to BigQuery directly. You can bring these into Yuki by updating the tool's connection string. |
| Not Routable | Queries that Yuki can't route. They're included in your total spend but can't be optimized. |
Which queries are Not Routable
Jobs from these sources are Not Routable:
| Source |
|---|
BigQuery internal: CDC merges (queueworker_) |
BigQuery internal: queueworker_ jobs |
| BigQuery internal: materialized view refreshes |
| BigQuery internal: metadata cache refreshes |
| Scheduled queries |
| Google Sheets |
| Looker Studio |
| Dataform |
| BigQuery console |
Where you see them
On the Cost & Savings page, Not Routable queries appear in the Cost Over Time chart:
- Break by Optimization Coverage. Not Routable spend is its own grey segment, next to Routed Through Yuki and Not Routed Through Yuki. The segment appears only when you have Not Routable spend in the selected range.
- Optimization Coverage filter. Choose Jobs Not Routable to show only these jobs.
How they affect coverage and potential savings
- Coverage. Optimization coverage is calculated out of the queries Yuki can route. Not Routable queries aren't counted, so they don't lower your coverage.
- Potential savings. Potential savings estimates what you'd save by routing your Not Routed Through Yuki queries through Yuki. Not Routable spend isn't included.