We need help identifying the server-side rejection reason for five distinct structured-output requests. All returned HTTP400 with the complete SSE error body below, without a rejected field/path or interaction ID. We have stopped inference calls; this is a request to investigate saved rejections, not to run new tests.
Endpoint: POST https://generativelanguage.googleapis.com/v1beta/interactions
Model: gemini-3.8-flash
Api-Revision: 2026-05-20
store=false, background=false, stream=true
generation_config={"max_output_tokens":24000}
response_format={"type":"text","mime_type":"application/json","schema":<saved schema>}
No tools, no code_execution, no previous_interaction_id, no explicit thinking_level.
Client: Node.js v24.19.0 native fetch; no Google SDK involved in the outbound POST.
The complete HTTP response body was:
event: error
data: {"error":{"message":"Request contains an invalid argument.","code":"invalid_request"},"event_type":"error"}
| Local label | Local request-start UTC | Local response-received UTC | Local SHA-256 prefix |
|---|---|---|---|
| R1/r5 | 2026-10-21T23:04:08.296Z | 2026-10-21T23:04:09.591Z | 89b25df733d197d9… |
| R2/r6 | 2026-10-21T23:11:24.204Z | 2026-10-21T23:11:26.424Z | 285f952146b4d819… |
| R3/r7 | 2026-10-21T23:15:49.439Z | 2026-10-21T23:15:50.991Z | 6dbd4c9072d5107c… |
| R4/r8 | 2026-10-21T23:19:33.811Z | 2026-10-21T23:19:35.285Z | 5172e438591583e0… |
| R5/r9 | 2026-10-21T23:22:46.239Z | 2026-10-21T23:22:47.638Z | 03d1dae30f4c993d… |
These are approximate local request-start/response-received UTC windows, not Google receipt timestamps. The SHA-256 values are local payload identifiers, not Google request IDs; they were not sent as IDs to Google. Only our x-request-id header lookup was persisted, and its result was null. We did not persist the remaining response headers. Full local hashes and exact schemas are retained and can be supplied privately.
A historical HTTP200 request used the same model, endpoint, non-secret controls, and transport implementation on 2026-10-21T07:48:50.350Z–2026-10-21T07:49:12.987Z. Its schema was 943 UTF-8 bytes/13 schema nodes. The five rejected schemas were 6816/14115/17025/107902/59232 bytes. We cannot establish a current server regression, a specific unsupported keyword, or the exact rejection cause from these differences alone.
- Can the Gemini API team locate any backend validation/grammar diagnostic for these historical requests using our project number (to be provided privately) and the UTC windows? Please confirm whether diagnostics are retained for store:false requests rejected with HTTP400, and the minimum identifiers needed if request IDs are unavailable.
- For each request, what exact parameter/schema JSON path and rule caused rejection? If it was a compiler-state/branching or nesting limit, please provide the relevant diagnostic and an actionable constraint, rather than assuming a specific keyword is unsupported.
- Does this exact model/API revision have any structured-output restriction relevant to these requests that is absent from the published guide? Please distinguish an unsupported keyword from a supported schema that exceeds compiler complexity.
- If no backend diagnostic is available, please state that explicitly and identify the smallest additional existing artifact needed to investigate without another inference call.
Please provide a private channel for the project number and exact schemas. The project associated with our configured execution credential has been confirmed locally and can be provided privately. The historical requests did not retain credential fingerprints. No project identifiers are included in this public post. We have not published prompts, customer data, credentials, API key values, or a complete private payload. Please do not replay the requests against our project or incur new billable inference without approval. If reproduction is essential, please advise first.
Documentation checked: