Receiving "Unsupported parameter: 'logit_bias'" Error with OpenAI O1 Model

Features
, ,
1

스크린샷 2024-12-17 오후 4.56.42
스크린샷 2024-12-17 오후 4.56.42898×1646 136 KB

Hi everyone,

I’m currently using the “Create a Completion” module in Make.com (formerly Integromat) with the OpenAI O1 model and encountering the following error message:

[400] Unsupported parameter: 'logit_bias' is not supported with this model.

I’ve reviewed my scenario settings and I don’t see any direct reference to logit_bias in the configuration. Yet, the request fails with this error. According to various discussions and documentation, this error suggests that the O1 model does not support the logit_bias parameter.

Here’s what I’ve gathered so far:

  • Model Compatibility: Not all OpenAI models support logit_bias, and newer models (like O1) may not allow it.
  • Platform-Specific Behavior: Some third-party tools or integrations might implicitly include logit_bias when calling the API, even if it’s not visible in the UI.
  • Azure OpenAI & API Versions: Users on Azure OpenAI have reported similar issues, indicating that certain models which previously supported logit_bias no longer do so. Changing the API version or model can sometimes resolve this.

Questions for the Community:

  1. Has anyone else encountered this error specifically when using the O1 model in Make.com’s OpenAI integration?
  2. Are there any known workarounds, such as switching to a different model or adjusting some hidden setting?
  3. Has anyone successfully disabled or removed logit_bias from Make.com’s OpenAI call parameters to prevent this error?

I’d appreciate any insights, tips, or guidance on how to resolve or work around this issue. Thanks in advance!

2 Likes
2

I have the same problem, same error. RuntimeError: [400] Unsupported parameter: ‘logit_bias’.
The error suggests that logit_bias is automatically being included in the request, even though it is not visible in the UI configuration.

2 Likes
3

Hello both @here, thank you very much for raising this in the community.

I just wanted to let you know that we have reported this issue to our development team who will look into it as soon as possible.

I will make sure to post any available updates here in this thread. If you prefer to receive updates in your inbox, please open a support ticket with our Care Team who will keep you posted on the progress.

We are very sorry for any inconvenience and disruptions this may be causing.
Thank you very much for your patience and understanding :pray:

4

same here and waiting for the solution,
thanks

5

Hi, same problem, thank you for your asap solution :pray:

6

I’m having the same problem.

7

Hello everyone @here,

Our developers have confirmed that a fix has been released. Could you please test on your end and see if everything works as expected?

If you’re still experiencing any issues, please open a support ticket with our Care Team who will investigate this further.

Once again, we apologize for any frustration and inconvenience by this.
Thank you for your patience and understanding.

1 Like
8

It works for me now. Thanks!

1 Like