Gemini 3.8 Flash HIGH: does maxOutputTokens include thinking tokens?

Thank you, @Sai_Deepika_K. The thinking guide now clarifies that maxOutputTokens includes thinking plus visible output. We kept the limit at 8192 rather than deliberately truncating at 100. Our remaining blocker is that generateContent returns HTTP 503 UNAVAILABLE before we receive usable output. Could you help us identify the right next diagnostic or route this for a project-specific review?

Latest controlled test (September 15, 2026)

  • Gemini Developer API, exact model gemini-3.8-flash, @google/genai 2.18.0, Node.js 24.19.0, Windows.
  • AI Studio shows the project on Free Tier. Before the test, its one-day view showed 0/5 RPM, 0/250,000 TPM and 0/20 RPD. We understand that the dashboard can lag by 15 minutes and does not reserve capacity.
  • models.get succeeds and advertises generateContent and thinking support; we do not interpret that as proof of generation capacity.
  • One text-only task, non-streaming, thinkingLevel MEDIUM, maxOutputTokens 8192, 300-second total timeout, JSON MIME with a seven-field responseJsonSchema. No attachments, tools, URL Context, explicit cache, fallback or model switching. Input was locally estimated at 921 tokens, not remotely measured.
  • We reused the previous HIGH test envelope, changing only the reasoning level and the local idempotency key. This is a later observation, not a simultaneous A/B experiment. Previous HIGH and MEDIUM tasks on separate days also failed.
  • UTC window: 2026-09-15 22:07:26.985 to 22:07:51.855. First call: 503 UNAVAILABLE. After 23.889 seconds, the only application-level retry: 503 UNAVAILABLE. Total elapsed: 24.870 seconds. SDK automatic retries were disabled with retryOptions.attempts=1. We stopped there.
  • No usable text, usageMetadata, modelVersion, request ID or Retry-After was observable through this SDK error path. This does not mean those headers were absent at the HTTP layer.

We read the pinned 429/503 guidance and the related 3.7/Priority discussion. We are not assuming that a different model or paid workload has the same cause as ours.

Remaining questions

  1. How can we distinguish ordinary Free Tier capacity shedding from a project-specific access or backend issue when every sampled generation fails but models.get works and displayed quota is unused?
  2. Is there a known issue for this exact model with non-streaming generateContent, MEDIUM/HIGH and responseJsonSchema? Which single request variable would you recommend testing next to isolate the cause?
  3. Is this pattern across several days expected for Free Tier, and is there an applicable incident/status entry or recovery guidance beyond generic retry advice?
  4. What bounded retry spacing do you recommend for this case, and which safe request identifier or header should we collect for support if the SDK does not expose it? We want to avoid retry loops.
  5. What minimum information is needed for a project-specific review, and which official private channel should receive it? We will not post credentials or private project identifiers publicly.
  6. Could you link the generateContent billing documentation supporting the statement that non-200 requests do not accrue billable output tokens? Please distinguish a server-returned 503 from a client timeout/disconnection after remote work may have started. The API-errors link currently describes Interactions API and I could not find that billing guarantee there.
  7. Would moving this exact model/workload to a paid tier materially change capacity availability, or only quota/priority? Is there a documented guarantee or evidence for that distinction? Billing remains disabled; we are not requesting an upgrade.
  8. Please confirm that the combined maxOutputTokens ceiling also applies with responseJsonSchema on this endpoint at MEDIUM/HIGH. The general ceiling is now clear; we have not been able to observe it in a successful generation.

Thank you. A concrete next diagnostic or the correct private escalation route would help us move forward without repeatedly consuming requests.