- snap-to-grid behavior;
- grid size of 10, 20, or 40 pixels;
- canvas hints;
- node descriptions; and
- confirmation before deleting a configured node.
What each setting changes
Grid changes are presentation aids. Execution uses stored nodes, edges, input bindings, and configuration, not canvas proximity. Hiding descriptions does not remove node type or accessible name from the graph.
For a large workflow, use the grid and consistent left-to-right lanes to make triggers, read-only processing, branch decisions, and side effects visually distinct. That convention helps review, but the edges and mappings remain the executable source of truth.
Keep configured-node delete confirmation enabled when workflows contain mapped values or high-impact actions; removing a node also removes its attached edges and can invalidate downstream bindings.
After deleting or replacing a node, run validation and inspect every downstream field that referenced it. A similarly named replacement node receives a new ID, so existing bindings are not automatically retargeted by its display name.
See Workflow editor for canvas behavior, Variables and data mapping for bindings, and Accessible editor for a non-canvas editing surface.