API-created workflows crash UI builder ("Something went wrong!")

[rickpixelml]

Workspace: 9a73fa8e-6202-43aa-8581-dffef27680fa

Broken workflow IDs:

3f0ff142-76bd-41ab-9b5e-31566bedae67
739b45b1-4d51-4b12-ba52-ecbdeabeab9d
b269f200-b5c2-4405-ae58-416a6a68163a

Environment:

AgenticFlow MCP Server (via Claude Code)
CLI: @pixelml/agenticflow-cli@1.0.7
API endpoints: create_workflow, update_workflow

Issue

Workflows created or updated via the create_workflow / update_workflow API render as "Something went wrong!" in the UI builder. The workflow page crashes and becomes inaccessible.

Key observations:

The same workflow executes correctly via execute_workflow API.
Workflows created manually in the UI work fine.
Copying a UI-created workflow via the UI copy button works, but updating the copy via the API breaks it again.
Workflow structure: 5-node pipeline — OCR → LLM (extract) → LLM (normalize) → LLM (transform) → API Call

User's hypothesis: The API does not populate internal UI metadata (node positions, layout coordinates, version fields, or other render-specific data) that the frontend builder requires. The workflow JSON is functionally valid but structurally incomplete for the UI.

Steps to Reproduce

1. Create a workflow via create_workflow API with valid nodes and correct model values from get_dynamic_options.
2. Open the created workflow in the UI builder.
3. UI crashes with "Something went wrong!"
4. Questions from User (need answers)

questions
Is there a known limitation with API-created workflows and the UI builder?
Are there additional fields we should include in the API payload for UI compatibility (e.g., node positions, layout metadata, version fields)?
Is there a recommended way to create workflows programmatically that remain fully renderable in the UI?

Expectation

Dev team to inspect the broken workflow IDs and compare their JSON structure with UI-created workflows.
Identify the missing metadata/fields that cause the UI crash.

Either:
(a) Fix the API to auto-populate required UI metadata on create/update, or
(b) Document the required additional fields so API consumers can include them, or
(c) Fix the frontend to gracefully handle workflows without UI layout metadata.

Respond to the user's 3 questions above.