n8n - 💡(How to fix) Fix Ask to reopen issue 15447 [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29091Fetched 2026-04-25 06:21:50
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2mentioned ×2subscribed ×2
RAW_BUFFERClick to expand / collapse

Bug Description

I'm facing same issue as https://github.com/n8n-io/n8n/issues/15447 but now with Gemini 3.1

Gemini 3.1 is only available on global https://docs.cloud.google.com/vertex-ai/generative-ai/docs/models/gemini/3-1-pro --> see supported region

I don't agree with the interpretation that adding global is an extra feature. Not having global as region make the use of Gemini model unavailable. So it's not a nice add-on.

To Reproduce

  1. Create a Gemini Model Node with gemini-3.1-pro-preview
  2. Create Google Service Account Credentials
  3. Launch the node --> No model found called 'gemini-3.1-pro-preview'

Expected behavior

Able to call gemini-3.1-pro-preview

Debug Info

Operating System

Cloud Run

n8n Version

2.17.7

Node.js Version

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The issue is likely due to the Gemini 3.1 model only being available in the global region, which is not specified in the node configuration.

Guidance

  • Verify that the Gemini 3.1 model is supported in the region where the node is being executed, as it is only available in the global region.
  • Check the documentation for the Gemini model to ensure that the correct region is specified in the node configuration.
  • Consider updating the node configuration to include the global region, as this may be required to access the Gemini 3.1 model.
  • Review the error message "No model found called 'gemini-3.1-pro-preview'" to ensure that the model name is correct and matches the one specified in the documentation.

Example

No code snippet is provided as it is not explicitly mentioned in the issue.

Notes

The issue may be specific to the n8n cloud hosting and the Gemini 3.1 model, and may not be applicable to other environments or models.

Recommendation

Apply workaround: Specify the global region in the node configuration to access the Gemini 3.1 model, as it is not available in other regions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Able to call gemini-3.1-pro-preview

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING