Use strict validation when saving rules
Strict validation in Zephr ensures rule integrity by identifying and managing unconnected and misconfigured nodes, preventing hard-to-debug issues.
Use strict validation to keep your Zephr rules tidy and avoid hard‑to‑debug issues caused by misconfigured nodes. When this feature is enabled, Zephr validates your rule graph each time you save a Feature or Redirect rule and helps you identify and manage nodes that are not part of an executable path or are incorrectly configured. Strict validation is especially useful when:
You want to keep the rule tidy without unconnected nodes in your rule
Extensions, webhooks or other components have been disabled/removed and you want to prevent these misconfigured nodes from being saved
Strict validation is controlled by a tenant-level feature flag. Contact Zuora Global Support if you want this feature enabled for your tenant.
What strict validation checks
When you save a Feature or Redirect rule in Rules Builder, Zephr performs the following checks.
Unconnected nodes (orphaned nodes) - Zephr scans the rule graph for nodes that are not reachable from the rule’s entry point.
Old branches that are no longer connected to any decision path
Outcomes or sub-trees left behind after refactoring a rule
These nodes are never executed, they add clutter and make the rule harder to read. If unconnected nodes are found, Zephr displays a confirmation dialog where you can choose one of the following options:
Remove and save - Zephr automatically deletes all unconnected nodes and saves a cleaned version of the rule.
Keep and save - Zephr saves the rule as-is and leaves the unconnected nodes in place.
Removing unconnected nodes is recommended in most cases because it reduces visual noise and makes the rule easier to understand and follow.
Misconfigured nodes - After handling unconnected nodes, Zephr checks the graph for nodes misconfigured . These nodes were previously valid but have lost their configuration. For example, a webhook or plugin node that referenced an extension which has since been disabled or removed. Misconfigured nodes are still part of an active path in the rule, so deleting them automatically could break the logical flow. Instead, Zephr:
Shows a summary of how many Misconfigured nodes exist in each user state (for example, Anonymous, Registered, or Customer) and whether they appear in sub‑rules.
Warns that these nodes are misconfigured and may cause unpredictable behaviour in the affected part of the rule.
Lets you choose to:
Go back and fix – Return to the rule canvas and manually repair or remove each Misconfigured node.
Save anyway – Keep the rule as-is and save despite the warning.
To fully resolve validation issues, you must manually update or remove each Misconfigured node and then save the rule.