You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7d1b047
Browse filesBrowse the repository at this point in the historyBrowse files
fix(workflows): accept json input type and return 400 for unsupported input types (#9342)
* fix(workflows): accept json input type and return 400 for unsupported input types
A Start/API trigger input field typed "json" (the name blocks use for objects) made manual and copilot runs fail with a 500, and broke MCP schema sync on deploy, because the shared run schema threw a plain Error on any type outside its list. Treat json as object and files as file[] everywhere the type is read, raise OrchestrationError('validation') for reserved names and unsupported types so callers answer 400 naming the field and allowed types, and canonicalize or reject input-format row types at write time.
* fix(workflows): sample aliased input types as their canonical type in mock payloads
* fix(mcp): answer an unpublishable workflow input as a validation failure
? 'Files: use an existing workspace file ID/key, a file upload {type:"file",data:"data:<mime>;base64,...",name}, or URL {type:"url",data:"https://...",name}. Stored metadata and access are rechecked when the workflow runs.'
0 commit comments