Conditional Custom Fields for Opportunities currently prevent a custom field from being used as a Trigger in one rule if the same field is already used as an Outcome in another rule.

This blocks legitimate hierarchical conditional logic.

Example:

Rule 1: Pipeline Stage = “On Market” → make “Urban Planning Check” mandatory.

Rule 2: “Urban Planning Check” = “Issues Found” → make “Issue Management” mandatory.

HighLevel rejects Rule 2 with the error:

“field used as condition here and outcome in the other rule.”

These rules do not conflict logically. Rule 2 is simply a child condition of Rule 1.

Please allow a field to be used as both an Outcome and a Trigger across different conditional rules, with cycle detection only where an actual circular dependency exists.

Also please consider removing or substantially increasing the current limit of 5 Outcomes per conditional rule. Complex Opportunity workflows frequently require more than five fields to be shown or made mandatory for the same Pipeline Stage.

This limitation currently forces unnecessary rule fragmentation and prevents clean multi-level conditional forms.