flow-step-development

State-based routing in chatbot workflow steps is added by defining success, error, and skip outcomes that connect to different downstream nodes across schemas, worker handlers, and builder viewers. This coordinates branching execution end to end without manual integration overhead.

State-based flow step routing is a mechanism defining success, error, and skip paths for chatbot workflow steps. It allows execution to branch to different downstream nodes based on worker execution results, while preserving fallback behavior when no edge is connected.

To wire a new flow step together, you update flow-config schemas, worker handlers, the React Flow builder viewer, and step registration in one coordinated workflow. This ensures schema design, worker execution, and visualization remain aligned for state-based routing.

Yes, you can define a skip path for chatbot flow steps when conditions are not met. State-based routing supports success, error, and skip outcomes, allowing steps to branch safely or skip execution while preserving fallback behavior when no edge is connected.

When no routing edge is connected to a chatbot workflow step, route fallback behavior is applied. This ensures the workflow continues execution safely even if success, error, or skip paths are not explicitly wired to downstream nodes.

Yes, React Flow handle mapping is required to build routed flow steps. It integrates with the builder viewer to visually map state-based routing outcomes, ensuring schema definitions and worker execution results align with the visual branching logic.