Provider changes/Google CloudGOOGLE CLOUD · VERIFIED CHANGE

Looker changes existing interface defaults

Looker changes existing interface defaults, string-filter behavior, database connection workflows, dashboard values, and data-lineage controls. Canadian time-zone changes also affect scheduling and now() calculations on unpatched instances starting November 1, 2026.

Verified Nov 3, 20265 official sources

Mentioned in the evidence

  • Looker (original)
  • Looker (Google Cloud core)
  • Looker scheduled content delivery and now() calculations
  • Looker Explore and merge query experience
  • Looker string filters and chart types Huh?

Official sources

  • Google Cloud changelog (changelog) ↗
    When you enter values in a string filter on dashboards, Looks, or Explores, clicking Done or clicking outside the input field no longer creates a filter chip from uncommitted text. To create a filter chip, press Enter, enter a comma (,), or paste values into the input field.
  • Google Cloud changelog (changelog) ↗
    Conversational Analytics DELETE endpoints now return HTTP 404 Not Found instead of HTTP 204 No Content when you attempt to delete nonexistent resources.
  • Google Cloud changelog (changelog) ↗
    The new Looker Explore and merge query experience is now generally available and is the default interface for Explores and for joining data from multiple queries.
  • Google Cloud changelog (changelog) ↗
    On the Token usage tab, the Conversational Analytics API value in the Feature column and the Feature Name filter has been renamed to Looker API. This value refers to the Conversational Analytics methods for the Looker This rename might cause a breaking change if you built custom
  • Google Cloud changelog (changelog) ↗
    The Use Legacy Connections Page legacy feature and the legacy database connection workflow have been removed. All database connections now use the connection workflow that is described in Connecting Looker to your database.

This is a global change, verified against Google Cloud’s own sources. It is not an assessment of your systems or your impact.

A global change is not your impact.

Auterim checks your confirmed dependencies and can verify repository references when GitHub is connected.