X-AI Grok Chat Modal report "Argument not supported on this model: presencePenalty"

[tienskowl]

Bug Description

When I use Grok-3 Modal, it will report an error as "Argument not supported on this model: presencePenalty".

To Reproduce

Ccreate a X-AI Grok Chat Node. Then trigger it.

Expected behavior

No error report and correct response sent

Operating System

Ubuntu 18

n8n Version

1.86.1

Node.js Version

N8n Docker version

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @tienskowl,

We have created an internal ticket to look into this which we will be tracking as "GHC-1556"

[douglasdgw]

n8n version

1.88.0 (Self Hosted)

Time

13/04/2025, 14:48:26

Error cause

{ "status": 400, "headers": { "access-control-allow-origin": "", "access-control-expose-headers": "", "cf-cache-status": "DYNAMIC", "cf-ray": "92fccb2d6da9f1c7-GRU", "connection": "keep-alive", "content-length": "111", "content-type": "application/json", "date": "Sun, 13 Apr 2025 17:48:19 GMT", "server": "cloudflare", "set-cookie": "__cf_bm=49FFU3P2.8rfNxDE1dr_NG38TdKMuw.IAp1MzHqF6K0-1744566499-1.0.1.1-KFfNIFow3IPnBh1K4aSGTl69ziue0yXNZ7Z8rfcG95E7mydAosSxUlkguQKhJrVW_pB.fSRL1rk804AIDLyy1flZaTdMma7J1FSmQoZaJZs; path=/; expires=Sun, 13-Apr-25 18:18:19 GMT; domain=.x.ai; HttpOnly; Secure; SameSite=None", "strict-transport-security": "max-age=31536000", "vary": "origin, access-control-request-method, access-control-request-headers" }, "error": "Argument not supported on this model: presencePenalty", "attemptNumber": 1, "retriesLeft": 2 }

[tutorempire]

Same issue here.

[anthonykhy]

Same issue with
n8n version

1.88.0 (Self Hosted)

[aktso]

Grok 3 beta is ok but not Grok 3 mini beta

[Elhard1]

same issue I can use grok 3 but no fast or mini models without the presencePenalty error

[ksokolovskiy]

Same issue with self-hosted

[cagbal]

Same here with grok 3 mini

[tutorempire]

This seems to be the same kind of issue as #14483

[douglasdgw]

Este parece ser o mesmo tipo de problema que # 14483

este citado ja esta fechado e é outro problema, um anterior a esse

[Elhard1]

I have developed a workaround for this problem and will post a pull request to fix this as soon as I get the time.

[trungmb007]

Same issue with self-hosted version 1.89.2

[overflood]

I'm experiencing the same error.
I may add, that this bug happens only with grok-3-mini-beta and grok-3-mini-fast-beta.
grok-3 (full) works fine.
So it looks like presencePenalty was always sent, but grok-3 full didn't worry about it, while grok-3-mini declines it completely.
While presencePenalty can be chosen in the parameters, it should not been sent, if not explicitly selected.

[SiuLeeBoss]

I'm also getting the same error, is there any progress on this error now?

[quangvinh2080]

I'm encountering the same issue

[kevin91nl]

^ I'm also encountering this error

[ersh11]

any solution ?

[overflood]

any solution ?

Seems it is fixed. Just curious when it will went in production, then we could test "normally"

[schrothbn]

any solution ?

Seems it is fixed. Just curious when it will went in production, then we could test "normally"

The fix was merged to master and therefore should be part of the next release

[thearrashedi]

Same issue with 1.93.0 (Self Hosted)

{ "status": 400, "headers": { "access-control-allow-origin": "", "access-control-expose-headers": "", "cf-cache-status": "DYNAMIC", "cf-ray": "948131096afb4bc3-BUF", "connection": "keep-alive", "content-length": "111", "content-type": "application/json", "date": "Fri, 30 May 2025 21:05:46 GMT", "server": "cloudflare", "set-cookie": "__cf_bm=o16gOQwKLFejWgEQJEjqI5L1YkikeY.JW7.UDnITzso-1748639146-1.0.1.1-pWzvkd6_KRYeLRakF2Iuk3ilzt1wI_PdiqO3INAhQ2jivxg_bATLiPpeylGhcaUUQpJh2TdnXYX5HaSvk7jAHPmMIK2KSbcO0.WdQ9or3r4; path=/; expires=Fri, 30-May-25 21:35:46 GMT; domain=.x.ai; HttpOnly; Secure; SameSite=None", "strict-transport-security": "max-age=31536000", "vary": "origin, access-control-request-method, access-control-request-headers" }, "error": "Argument not supported on this model: presencePenalty", "attemptNumber": 1, "retriesLeft": 2 }

[ersh11]

any solution ?

Seems it is fixed. Just curious when it will went in production, then we could test "normally"

The fix was merged to master and therefore should be part of the next release

Was it confirmed to be an n8n issue? I'm already on the latest version 1.94.1 and I still happening

[schrothbn]

any solution ?

Seems it is fixed. Just curious when it will went in production, then we could test "normally"

The fix was merged to master and therefore should be part of the next release

Was it confirmed to be an n8n issue? I'm already on the latest version 1.94.1 and I still happening

The fix is not part of the latest release. As I mentioned it’ll be in next release. Next release is going to be 1.95. 1.94.1 was done before the fix was merged. It’s planned for next Monday but you can follow the release notes or the merged PR to stay up to date. Every PR gets marked when it’s part of a release and the version it’s part of will be in the comments on the PR.

[ariangibson]

Just confirming the fix did not make it into 1.95.X. However, it did make it into 1.97.0 - I just tested it with 1.97.0 (Pre-Release) and Grok 3 Mini works perfectly, now. Thanks, team!