Plugin Azure OpenAI version 0.0.55 does not support enabling structured JSON output on LLM nodes.

[ArtemisYi]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.3

Plugin version

0.0.55

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This situation has occurred before. At that time, I also submitted an issue, and the problem was resolved.
(#2706)
However, now when I try to switch to GPT-5.4, the issue of not being able to output JSON correctly has reappeared.
I have confirmed that my plugin is updated to the latest version 0.0.55, and that my API is responding normally.
When I switch back to 0.0.39 and use gpt-5 (this version cannot use gpt-5.4), it still works fine.

My json schema:

{
  "additionalProperties": false,
  "properties": {
    "research_subject": {
      "properties": {
        "clinical_patients": {
          "description": "涉及真实人类患者或临床样本",
          "type": "boolean"
        },
        "drug_ingredients": {
          "description": "以药物或化合物本身为核心研究对象",
          "type": "boolean"
        },
        "economic_animals": {
          "description": "涉及家畜、家禽等经济动物",
          "type": "boolean"
        },
        "economic_plants": {
          "description": "涉及农作物等经济植物",
          "type": "boolean"
        },
        "human_cells_in_vitro": {
          "description": "涉及人类细胞系（如HeLa, 293T）或体外生化模型",
          "type": "boolean"
        },
        "microorganism": {
          "description": "涉及细菌、真菌、病毒等微生物",
          "type": "boolean"
        },
        "model_animals": {
          "description": "涉及小鼠、大鼠等实验室活体模式动物",
          "type": "boolean"
        },
        "model_plants": {
          "description": "涉及拟南芥等模式植物",
          "type": "boolean"
        }
      },
      "required": [
        "clinical_patients",
        "human_cells_in_vitro",
        "microorganism",
        "drug_ingredients",
        "economic_animals",
        "economic_plants",
        "model_animals",
        "model_plants"
      ],
      "type": "object"
    }
  },
  "required": [
    "research_subject"
  ],
  "type": "object"
}

✔️ Error log

[models] Bad Request Error, Error code: 400 - {'error': {'message': "Invalid schema for response_format 'llm_response': In context=('properties', 'research_subject'), 'additionalProperties' is required to be supplied and to be false.", 'type': 'invalid_request_error', 'param': 'text.format.schema', 'code': 'invalid_json_schema'}}

[dosubot]

This is the same class of bug you hit before in #2706. The root cause is that the plugin's _adapt_schema_for_structured_outputs() method does not automatically inject additionalProperties: false into nested objects — it only handles the required field enforcement and null-union conversions [1].

Azure's Responses API (which GPT-5.4 is routed to) requires additionalProperties: false to be explicitly present on every object in the schema, not just the root. Your schema has it at the root level but is missing it on the nested research_subject object, which is why you see:

In context=('properties', 'research_subject'), 'additionalProperties' is required to be supplied and to be false.

Immediate workaround: Add "additionalProperties": false to your research_subject object definition:

"research_subject": {
  "additionalProperties": false,
  "properties": { ... },
  "required": [ ... ],
  "type": "object"
}

Why this regressed: The fix in v0.0.48 (which resolved your earlier issue #2706) addressed the root-level additionalProperties requirement, but the plugin still doesn't recursively add it to nested objects [1]. GPT-5.4 goes through the same Responses API path as other GPT-5 models, so the stricter schema validation applies.

This is a legitimate bug — the plugin should be automatically adding additionalProperties: false to all nested objects when adapting schemas for the Responses API, the same way it already handles the required field recursively.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.