GCP Release Notes: October 14, 2025

GCP Release Notes: October 14, 2025

BigQuery

Feature

You can now use SQL cells to write, edit, and run SQL queries on your BigQuery data directly from your notebooks. This feature is in Preview.

Announcement

The BigQuery Data Transfer API (bigquerydatatransfer.googleapis.com) is now enabled by default for every new Google Cloud project. This feature is generally available (GA).

Feature

You can now embed natural language as comments in existing SQL to refine and transform your code. This feature is preview.

Colab Enterprise

Feature

SQL cells

Preview: You can use SQL cells to write, edit, and run SQL queries directly from your Colab Enterprise notebooks. For more information, see Use SQL cells.

Gemini Code Assist

Breaking

Gemini Code Assist tools are no longer available and are replaced by agent mode (Preview)

Effective October 14, 2025, Gemini Code Assist tools are no longer available. This completes the deprecation process that was announced on October 2, 2025.

Using the @ symbol followed by the name of a tool no longer connects to Gemini Code Assist tools.

To connect to external services, use Model Context Protocol (MCP) servers in Gemini Code Assist agent mode.

For more information, see:

Google Cloud Contact Center as a Service

Announcement

Portal version 3.40 pre-release notes

Here are the pre-release notes for portal version 3.40. When we release version 3.40, we expect the new capabilities to be as shown here.

Feature

New variables for custom lookup URLs

We’ve added the following five variables for custom lookup URLs:

  • CUSTOMER_PHONE_NUMBER: the end-user’s phone number
  • SUPPORT_PHONE_NUMBER: your call center’s phone number that an end-user calls in on
  • OUTBOUND_NUMBER: the phone number an agent uses when making an outbound call
  • SESSION_ID: the session ID
  • CUSTOM_AGENT_ID: an optional agent ID

Feature

Agent desktop maintains state after refresh

While you’re using the agent desktop, if you refresh your browser, the agent desktop now maintains its state. This means that active conversations, finished tabs, and recently closed sessions remain as they were before the refresh.

Feature

Search in email channel by email address and name

Agents can now search for email sessions by email address and name in the email adapter.

User experience change: The search pane in the email adapter includes two new fields: Email Address and Name.

Feature

Customize the color of the Start Screen Share button

You can now control the color of the Start Screen Share button to match the color palette of your brand.

Feature

The europe-west4 and europe-west6 regions are available for Agent Assist conversation profiles

The europe-west4 and europe-west6 regions are now available when you create an Agent Assist conversation profile for a Dialogflow CX virtual agent. For more information, see Create conversation profile for Dialogflow CX virtual agents.

Feature

Web SDK: Support for hiding the download transcript option

You can now configure the web SDK to do the following on the end-user’s chat screen:

  • Hide the Download transcript menu option during a chat session

  • Hide the Download transcript button after a chat session ends

Feature

Web SDK: Support for hiding the Start a new conversation button

You can now configure the web SDK to hide the Start a new conversation button on the end-user’s chat screen after the session ends.

Fixed

The following issues were addressed in this release:

  • Fixed an issue that prevented administrators from configuring virtual agents on the top level for IVR queues.

  • Fixed an issue where attempting to configure automatic redirection settings for the top level of an IVR queue returned an error.

  • Fixed in issue that caused incorrect agent monitoring and reporting data when a virtual agent escalated a call to a queue in a different language.

  • Fixed issue for HubSpot users where the call adapter got stuck on a non-functional reconnect page after a session expired.

  • Fixed an issue for HubSpot users where the Delay call record creation until the call is connected to agent checkbox didn’t appear in the CRM Record Creation Details pane.

  • Fixed an issue that prevented agents from ending direct SMS chat sessions.

  • Fixed an issue for Microsoft Windows 11 users that prevented agents from entering Japanese characters in the chat screen during chat sessions and into the notes during wrap-up.

  • Fixed an issue where SDK custom data that was passed using the web SDK didn’t appear in the agent adapter.

  • Fixed an issue that prevented custom links entered in the chat adapter from being converted into clickable links.

  • Fixed an issue in the chat screen of the chat adapter where the Missed target response time message was partially obscured by the formatting toolbar.

  • Fixed an issue where agents couldn’t initiate a callback to a missed agent-to-agent call from the History tab of the agent adapter.

  • Fixed an issue where predictive outbound calling campaigns stalled and incorrectly moved contacts to the Redialed list before retrying them. This prevented the campaigns from completing successfully.

  • Fixed an issue in the Call Details pane where the Recording Message Sequence settings were incorrectly inactive when the Play Call Recording Messages checkboxes were cleared.

    Administrators: In the Call Details pane, we changed Recording Message Sequence to Recording Message Sequence for Outbound Calls for clarity.

  • Fixed an issue where the customized greeting for an automatic redirection rule didn’t play for calls that entered the queue using a Direct Access Phone (DAP) number.

  • Fixed an issue that occurred when a call was made from the global contact list. On the Details tab of the call adapter, the destination name didn’t display. Instead, the destination phone number displayed.

  • Fixed an agent desktop issue where an agent status that was configured with a role restriction mistakenly appeared in the status list for a user assigned to that restricted role.

  • Fixed an issue where searching for an inbound-only queue on the Phone Number Management page failed to return a result.

  • Fixed an issue that caused queue duration and wait duration to be reported as 0. This occurred when the Call Service Level Target on a queue settings page was set to a number that exceeded the maximum allowed limit.

  • Fixed an issue where a team assigned to a preference profile added only 1 user to the profile’s users count, instead of adding the total number of users on the team.

  • Fixed an issue where agents were timed out for inactivity while composing an email in the email adapter.

  • Fixed an issue where users with a custom role were unable to save changes in the Chat Settings pane, even when their role had View and Edit permissions.

  • Fixed an issue that occurred after an agent configured their own hours of operation settings in the agent adapter. Those settings didn’t appear for administrators in the agent’s user profile on the Settings > Users & Team > Manage Users & Teams page. This prevented the administrator from making other edits to the agent’s profile without overwriting the agent’s hours of operation settings.

  • Fixed an issue where CRM tickets weren’t created for some calls.

  • Fixed an issue where outbound SIP calls incorrectly appended data parameters, causing calls to fail.

Google Kubernetes Engine

Issue

In GKE versions 1.32.4-gke.1029000 and later, MountVolume calls for network file system (NFS) volumes might fail with the following error: mount.nfs:rpc.statd is not running but is required for remote locking.

This failure can occur if a Pod mounting an NFS volume runs on the same node as an NFS server Pod, and the NFS server Pod starts before the client Pod attempts to mount the volume. This scenario causes a conflict over the rpcbind service, which prevents the service from starting correctly on the node for the client Pod, leading to the mount failure.

As a workaround, deploy this DaemonSet on all nodes where you mount the NFS volumes. The DaemonSet ensures that the required services start correctly.

Source: Google Cloud Platform

Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *