What's happening
On solution pages, the Workflow canvas section renders maker Notes as
graph nodes. Because they're drawn with the same node styling as real steps, they
appear to be part of the process flow, sometimes connected directly to other
nodes, sometimes floating unconnected on the canvas.
Notes are informational annotations that makers place on the design canvas for
context/documentation. They are not executable steps (classification, condition,
loop, agent call, human review, etc.). Rendering them as nodes:
- Misrepresents the actual workflow logic (adds "steps" that don't exist).
- Creates confusing edges/floating boxes that imply flow that isn't there.
- Makes the canvas harder to read and the solution harder to understand.
Suggested fix
When building the canvas from the saved designer graph in the exported solution,
filter out note/annotation entities (and any edges attached to them) from the node
set used for the process visualization.
What's happening
On solution pages, the Workflow canvas section renders maker Notes as
graph nodes. Because they're drawn with the same node styling as real steps, they
appear to be part of the process flow, sometimes connected directly to other
nodes, sometimes floating unconnected on the canvas.
Notes are informational annotations that makers place on the design canvas for
context/documentation. They are not executable steps (classification, condition,
loop, agent call, human review, etc.). Rendering them as nodes:
Suggested fix
When building the canvas from the saved designer graph in the exported solution,
filter out note/annotation entities (and any edges attached to them) from the node
set used for the process visualization.