Displaying warning messages about workflow validation is meaningless to users.

[jtydhr88]

While loading some workflows, the frontend displays warnings such as "Invalid workflow against zod schema: Validation error: Invalid uuid at "id".

Firstly, zod schema information is too technical for end users.

Secondly, this warning doesn't affect the actual workflow execution.

And what's the point of displaying this information? Is it to encourage users to fix the workflow?
But almost no workflow author understands what zod schema means and how to fix it.

Furthermore, this warning cannot be disabled; it reappears every time the workflow is closed and reloaded, which is very annoying.

sharp_basic.json

We should provide a "fix" button so users can fix these warnings with a single click; otherwise, we should remove similar warnings from the front-end page (or at least put them in the browser console instead of displaying them on the page all the time).

┆Issue is synchronized with this Notion page by Unito

[dosubot]

These Zod schema validation warnings appear because the frontend validates workflow files against a strict schema and displays any errors as UI alerts using the toast notification system. The technical details (like “Invalid uuid at 'id'”) come directly from the schema validator and are not tailored for end users. There’s currently no UI or config option to suppress these warnings—they will always show unless the code is changed to silence them, which is not possible from the user side. This has been reported by many users and is recognized as a UX issue: the warnings are confusing, not actionable for most users, and do not affect workflow execution if the workflow still runs as expected. Maintainers have discussed making these messages more user-friendly or only showing them to developers, but as of now, there’s no permanent fix or toggle for end users. For now, if your workflow runs, you can safely ignore these warnings, though they will keep appearing on reloads until the frontend’s error handling is improved.
See code and discussion
See implementation details

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

[jtydhr88]

@dosu as I mentioned, We should provide a "fix" button so users can fix these warnings with a single click; otherwise, we should remove similar warnings from the front-end page (or at least put them in the browser console instead of displaying them on the page all the time).

[dosubot]

Currently, the only automated "fix" in the frontend is for broken or invalid links—handled by the fixBadLinks utility, which is already used during workflow validation. There’s no general-purpose auto-fix for other schema errors like invalid UUIDs or aux_id fields, so a "fix" button would only be able to repair links unless new utilities are developed to handle other error types.

To suppress or relocate these technical warnings, the validation logic does support a silent flag that, if exposed in the UI, could redirect warnings to the browser console instead of showing them as toast notifications. However, this is not currently user-configurable—warnings always appear as UI alerts unless the code is changed to set silent=true or to log errors to the console instead of the UI toast system.

To address your suggestions, the codebase would need: (1) a UI button that triggers the existing link-fixing logic (and future auto-fix utilities as they are developed), and (2) a settings toggle to suppress or redirect validation warnings away from the main UI. Right now, only link fixing is feasible with a one-click button; other schema errors would require more complex, targeted fixes to be implemented first.
See code and discussion

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}