Environment: Gemini Developer API (generativelanguage.googleapis.com), @google/genai 2.8.0 (Node), models gemini-3-flash-preview and gemini-3.5-flash, reproduced 2026-06-16. Affected under default Api-Revision and explicit 2026-05-20.
Summary: Continuing an interaction via previous_interaction_id returns 501 not_implemented whenever the prior interaction's stored steps contain built-in server-side tool steps (google_search_call/_result or code_execution_call/_result). The seed completes fine; only the continuation fails. Contradicts the Tool-Combination / Google-Search docs, which state continuing a grounded interaction via previous_interaction_id is supported on Gemini 3 with server-managed id/signature. Worked previously → recent server-side regression.
Repro / scope / cause: see the "Minimal reproduction", "Root cause" and "Mechanism" sections above. Not fixable client-side (tested Api-Revision, apiVersion v1beta/v1alpha). Custom function-calling continuation is unaffected.
import { GoogleGenAI } from "@google/genai"; // 2.8.0
const client = new GoogleGenAI({ apiKey: process.env.GEMINI_API_KEY });
const seed = await client.interactions.create({
model: "gemini-3-flash-preview", // also repros on gemini-3.5-flash
input: "Who won Euro 2024?",
tools: [{ type: "google_search" }],
}); // seed.status === "completed"
await client.interactions.create({
model: "gemini-3-flash-preview",
previous_interaction_id: seed.id,
input: "Who was the top scorer?", // plain text, no tools
}); // => 501 not_implemented
Secondary observation: the url_context built-in tool currently returns a spurious 400 "safety violations (harmful content)" on benign URLs (e.g. en.wikipedia.org/wiki/Coffee).
Environment: Gemini Developer API (generativelanguage.googleapis.com), @google/genai 2.8.0 (Node), models gemini-3-flash-preview and gemini-3.5-flash, reproduced 2026-06-16. Affected under default Api-Revision and explicit 2026-05-20.
Summary: Continuing an interaction via previous_interaction_id returns 501 not_implemented whenever the prior interaction's stored steps contain built-in server-side tool steps (google_search_call/_result or code_execution_call/_result). The seed completes fine; only the continuation fails. Contradicts the Tool-Combination / Google-Search docs, which state continuing a grounded interaction via previous_interaction_id is supported on Gemini 3 with server-managed id/signature. Worked previously → recent server-side regression.
Repro / scope / cause: see the "Minimal reproduction", "Root cause" and "Mechanism" sections above. Not fixable client-side (tested Api-Revision, apiVersion v1beta/v1alpha). Custom function-calling continuation is unaffected.
Secondary observation: the url_context built-in tool currently returns a spurious 400 "safety violations (harmful content)" on benign URLs (e.g. en.wikipedia.org/wiki/Coffee).