Silent failure when hitting max_output_tokens limit in Responses API

I’ve just described this issue in another topic.

Basically, if you are using prompt IDs, there might be a ‘legacy’ value that is messing around with your requests.

ps: it seems to be unrelated to legacy. I tested a new prompt, and confirmed that it was affected too.