Saving a json_schema response format works once. Reopening the Advanced UI shows a massively duplicated required array. This is not on every json_schema but probably Running the workflow throw an error. Any attempt to edit/remove items or switch output type triggers:
can't access property "push", a.required is undefined
This leaves the step stuck: you can’t clean the schema or change the output type.
Expected
-
The editor preserves a unique required array.
-
Removing required items or switching output type doesn’t crash the UI.
Actual
-
On reopen, required contains hundreds of duplicates of the same 3 keys.
-
Deleting/adding items or changing output type throws a.required is undefined.
-
State becomes uneditable.
-
Page crash on selection of output format “Text”
Steps to Reproduce
-
Create a step with response_format.type = “json_schema” named PhotoQuestQuestion.
-
Paste this valid schema, Save:
{
“type”: “object”,
“title”: “PhotoQuestQuestion”,
“description”: “A structured multiple-choice question generated from a newspaper photo.”,
“properties”: {
“question”: { “type”: “string”, “description”: “The question related to the newspaper page.”, “default”: “” },
“answers”: {
“type”: “array”,
“description”: “An array of 4 possible answers. One is correct; the other three are incorrect.”,
“items”: { “type”: “string”, “description”: “A possible answer to the question.” },
“minItems”: 4, “maxItems”: 4, “default”:
},
“correct_answer_index”: { “type”: “integer”, “description”: “The index (0-based) of the correct answer in the answers array.”, “minimum”: 0, “maximum”: 3 }
},
“required”: [“question”,“answers”,“correct_answer_index”],
“additionalProperties”: false
}
-
Reopen the schema editor. The required array is now duplicated many times.
-
Try removing items or changing output type → error a.required is undefined.
-
Attempting to remove schema elements also fails with the same error.
Impact
-
Cannot correct the schema.
-
Cannot switch the output type.
-
Workflow step is effectively bricked unless recreated under a new name.
UPDATES:
This is due to a data transformation that happens after the agent workflow