If I request a function to be called, gpt-4-1106-preview calls the function with parameters that have wrong UTF-8 encoding for non-ascii characters (international alphabets). Sometimes the characters are left out, sometimes they are just random and sometimes it uses HTML encoding. The same call wor…

Hi, thank you for the ping :slight_smile: The newly released gpt-4-0125-preview, as well as the upcoming gpt-3.5-turbo-0125, fixes these issues! Thank you for your patience while we addressed this. We will keep this thread open until the release of gpt-3.5-turbo-0125. Enoch

Now it is even worse! Now both gpt-3.5-turbo-1106 and gpt-4-1106-preview models generate incorrect results.

Chiming in to report that I’m also experiencing server-side encoding issues which started recently (less than 7 days ago) on gpt-3.5-turbo-1106 with the function tool. I’m using the chat completion endpoint to ask the model to call a function with a single value argument from an enum. One of the va…

Hi, as @juria rightly pointed out, the problem for at least 2 days (2 days ago my project stopped working properly) also affects the gpt-3.5-turbo-1106 model with the function tool. Since then, 70-80% of queries end up with a 500 error (and what’s worse, charging a query fee nonetheless. I don’t kno…

Same observation here for any -1106 model; French chars with diacritics end up corrupted by the model : bÅuf / pÃ©rÃ©grination / dÃ©saccord. Among the fix beeing a total fail and the warning removed without any decent reason, it’s now worse than before. That situation is severely frightening about…

I experienced the same issue with the function-calling tools. I defined function arguments like : { "name":"ScalpProperties", "description":"Propriétés du cuir chevelu", "parameters":{ "type":"object", "properties":{ "cuir_chevelu":{ "type":"…

Has it been fixed? gpt-3.5-turbo-1106

This is a complete mess! We have to shut down our complete service if this can’t be fixed soon. If possible, do a roll back of that previous bug fix.

Same issues here, now also with gpt-3.5-turbo-1106, not only gpt-4-1106-preview. Hope this isn’t the model itself (shouldn’t be since it works fine without function calling). We need a real fix here, impossible to do ourselves!

I am also waiting for them to fix this error. It makes it very difficult to move software to the production level.

Gpt-4-1106-preview messes up function call parameters encoding

API Bugs

louis.antonini December 3, 2023, 10:41pm 36

The fix indeed made it worse, and impossible for us here in the nordics to use the function calls.

Topic		Replies	Views
GPT 4.1 Character Encoding Issues? Bugs gpt-4-1	29	5008	December 3, 2025
The GPT-4-1106-preview model keeps generating "\\n\\n\\n\\n\\n\\n\\n\\n" for an hour when using functions API chatgpt , api	9	2767	December 31, 2023
Massive Token Overestimation in Multiple Tool Calls due to Internal Unicode Escaping Bugs bug , token , api-billing	9	323	March 12, 2026
Json format causes infinite "\n \n \n \n" in response API gpt-4 , api , json-mode	21	11069	April 30, 2025
Bad results when using fine-tuned model with function calling API fine-tuning , function-calling , fine-tuning-problems	15	5002	November 23, 2023

Gpt-4-1106-preview messes up function call parameters encoding

Related topics