Which hit policy in the Decision Object causes an error due to overlapping logic?

The unique hit policy in a Decision Object defines that for each input, there must be a single, unambiguous output. When multiple inputs lead to overlapping conditions that could yield more than one output, the unique hit policy will result in an error. This is because the system cannot determine which of the conflicting conditions should apply, leading to ambiguity in the decision-making process.

In a unique hit policy, each condition must be distinct and clearly defined without overlaps. If any two rules could potentially trigger for the same input, you would encounter an error. The nature of this policy ensures clarity and precision in decision outcomes, making it crucial to structure the rules in such a way that they do not intersect.

The other hit policies function differently, with either a priority assigned to determine outcomes or allowing for multiple outputs, which do not inherently cause conflicts in logic in the same manner as the unique policy. Therefore, the uniqueness of conditions is central to the handling of decision logic under this particular hit policy, leading to an error when any overlapping logic is present.