Diagnostics & Suggestions

Flow Builder continuously analyzes the graph as you edit it. The top bar separates implementation problems from business guidance:

• Errors , the flow is not valid enough to continue or execute.
• Warnings , something is likely incomplete or risky, but it may not be a hard blocker by itself.
• Suggestions , optional, evidence-backed improvements to completeness, revenue, trust, or operations.

Errors point to a concrete configuration gap and provide a direct action.

Errors

Errors are correctness failures. Examples include:

• a Work Order Form has no published form selected;
• a Tiers node has no tiers;
• a Conditional has no variable or comparison value;
• a Splitter has no switch variable or cases;
• a case output or required branch is unconnected;
• a variable source appears after the node that tries to read it;
• a Work Order Form is disconnected from the service-completion path;
• a Stint is missing Servo Types or its Servo Types node is not connected to Servo.

The error panel exposes Go to source and, when the rule knows the exact fix, an action such as Select a form. Fix the node, then re-check the top bar. Blocking errors keep Next disabled.

Warnings

Warnings describe a flow that may technically exist but will probably produce a bad experience or an incomplete result. Examples include:

• all tiers are still priced at 0;
• a Calculator has outputs but no incoming user-flow connection;
• a Conditional has a configured branch whose True or False output is not connected;
• a node is isolated from the rest of the graph;
• Servo Types or Servo connections are incomplete.

Warnings usually offer Open the setting, Go to source, or a similar focused action.

Warnings explain the risk while leaving the author in control of the flow.

Business suggestions

Suggestions are deterministic business rules, not opaque model output. The same graph produces the same suggestions because the rules inspect the flow type, nodes, edges, and relevant configuration.

Suggestions are grouped into four categories:

Category	What it looks for
Completeness	Missing linked page/entity, missing pricing, or a quote that cannot complete the journey.
Revenue	Tiered options, add-ons, tax, tips, payment methods, deposits, and minimum charges.
Trust	Rental rules and other expectations that should be explicit before payment.
Operations	Scheduling, pickup locations, long forms, branching, policies, and invoice templates.

Each suggestion includes:

• an impact level such as High impact, Medium impact, or Nice to have;
• a short explanation of the business reason;
• Why this appeared evidence tied to the current graph;
• an action such as Connect a page, Add Checkout, Set the tax rate, or Go to source;
• Dismiss when the recommendation is not appropriate.

Suggestions turn the current graph into a practical improvement list.

Common examples include:

• Connect this flow to a page when nodes exist but no published page is linked;
• Nothing in this flow sets a price for a service or rental with no pricing node;
• Quotes stop short of a sale when Quote exists without Checkout;
• Offer good / better / best when a money flow has no Tiers node;
• Sell add-ons before checkout when payment follows directly after the main selection;
• Let customers pick a time when a service/rental/event flow has no Scheduling node;
• Attach an invoice template when a Calculator has no invoice template.

Suggestions are capped so the panel remains a prioritized to-do list rather than a wall of advice.

Why the panels are different

The three panels answer different questions:

Errors      Can this graph work?
Warnings    Is something likely to go wrong?
Suggestions How could this graph perform better?

Fix errors first, review warnings next, and use suggestions to improve a flow that already has a valid structure.