Condition panel and saved XML disagree for a labeled parameter condition

Title: Labeled parameter condition saved with min > max never triggers

FMOD Studio version: 2.04.[xx]
OS: [Windows 11]

A trigger condition on a labeled parameter can be saved in the event XML with a minimum greater than its maximum. FMOD Studio displays it as a normal single-label condition, but it never evaluates true. The UI and the saved data disagree, and nothing in the UI shows it.

here is a screenshot and the relevant XML

Several instruments in the same event have the same three trigger conditions on one labeled parameter, combined with OR: Walk (value 0), Step (value 5) and DragStep (value 6). The Conditions panel looks exactly like this for every one of them:

But the saved XML is not the same. Instrument A (works):

<object class="MultiSound" id="{instrument-A}">
    <property name="triggerConditionMode">
        <value>1</value>
    </property>
    <relationship name="triggerConditions">
        <destination>{A-condition-1}</destination>
        <destination>{A-condition-2}</destination>
        <destination>{A-condition-3}</destination>
    </relationship>
</object>
<object class="ParameterCondition" id="{A-condition-1}">
    <property name="minimum"><value>0</value></property>
    <property name="maximum"><value>0</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>
<object class="ParameterCondition" id="{A-condition-2}">
    <property name="minimum"><value>5</value></property>
    <property name="maximum"><value>5</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>
<object class="ParameterCondition" id="{A-condition-3}">
    <property name="minimum"><value>6</value></property>
    <property name="maximum"><value>6</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>

Instrument B (never triggers on Step). Only the second condition differs:

<object class="ParameterCondition" id="{B-condition-1}">
    <property name="minimum"><value>0</value></property>
    <property name="maximum"><value>0</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>
<object class="ParameterCondition" id="{B-condition-2}">
    <property name="minimum"><value>5</value></property>
    <property name="maximum"><value>0</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>
<object class="ParameterCondition" id="{B-condition-3}">
    <property name="minimum"><value>6</value></property>
    <property name="maximum"><value>6</value></property>
    <relationship name="parameter"><destination>{labeled-parameter}</destination></relationship>
</object>

(GUIDs replaced with placeholders. Other properties of the instruments are omitted.)

Result: with the parameter set to Step, instrument A plays and instrument B is silent, although both show “Step” in the Conditions panel.

Expected: FMOD Studio should not save a labeled parameter condition with minimum > maximum, or it should show the condition as invalid (in the UI or in project validation).

I have not found a way to reproduce it; the values were already present in older saves of my project. Renaming the event, moving it to another folder or changing its bank assignment and saving keeps the inverted values. Duplicating the event fixes it: in the copy every condition is saved with minimum = maximum. Removing the condition and adding it again also fixes it.

Is this a known issue, and is there a known way a condition ends up like this?