I updated yesterday [1] and now there are a lot of errors in the logs: Discourse AI: structured output response was not valid JSON, falling back to best-effort parsing (311 bytes) I inspected the HTTP response and it had no issue. Then I tried the text with rails console: ... discourse(prod)> p =…

[imagen] lilydjwg: and now there are a lot of errors in the logs: That is a warning, not an error. That said, I’m moving that to INFO log level, as people keep getting worried about these :face_exhaling:

[imagen] Falco: That is a warning, not an error. Well, technically true, but it indicates a bug in the code. The fallback works so no error is raised, but it is better to fix the source instead of moving it to INFO level to cover up, isn’t it? JSON allows line feed charaters as whitespace bu…

To illustrate, the following is valid JSON: { "key": "value" } The following is an escaped one, which is invalid and causing the issue: {\u000a "key": "value"\u000a}

Discourse AI: la respuesta de salida estructurada no era JSON válido

Soporte

Falco (Falco) 29 Julio, 2026 15:00 2

Eso es una advertencia, no un error.

Dicho esto, voy a cambiarlo al nivel de registro INFO, porque la gente sigue preocupándose por esto

Tema		Respuestas	Vistas
Translation silently truncated when JSON stream parsing breaks (no error raised) Bug ai , dynaloc	2	128	14 Julio 2026
JSON API parsing error, single quotes used for errors like "['BAD CSRF']" Bug	2	1408	16 Marzo 2017
Error on ask.discourse.com: SyntaxError: Unexpected end of JSON input Bug ask-discourse	3	155	10 Julio 2025
AI translations errors Bug ai	10	249	10 Mayo 2026
Improve BAD CSRF error message when making API calls with content-type application/json Development	4	4361	14 Septiembre 2020

Discourse AI: la respuesta de salida estructurada no era JSON válido

Temas relacionados