Runtime behavior and troubleshooting

Use this checklist when a v2 condition appears to save but does not behave as expected.

Verify the trigger

1. Confirm the rule is enabled and that the published form contains the latest saved document.
2. Use the field's internal name, not its visible label. Names are case-sensitive and composite controls may use dotted paths (for example, fullName.First).
3. For choice fields, compare the stored option value exactly. A label that looks identical can still differ by whitespace, capitalization, or an imported value.
4. Check the match mode: AND requires every statement; OR requires one statement.
5. Check the operator and data type. Numeric comparisons require numeric-compatible values; is empty and is filled do not take a comparison value.

Verify the target

• The target must already exist in the form; show/hide-multiple does not create fields.
• A hidden field is removed from the respondent's visible path. Do not make a field required unless the condition can reveal it, or test that the submission engine ignores hidden required fields in your exact form.
• If two rules affect one target, simplify them or test both combinations explicitly. Do not rely on rule order as precedence.

Formula and default-value checks

• Put field references in braces ({quantity} * {unit_price}); keep source and target fields distinct to avoid circular updates.
• Test empty, invalid, zero, decimal, and boundary inputs. A calculated value is convenience logic, not a security boundary; recalculate and validate sensitive values on the server.
• Default Values are scalar prefills. Confirm the field name and value type, then test both the untouched form and a respondent-overridden value.

Published-form checks

Preview can use an unsaved editor document while a public URL uses the last published version. Save, publish, hard-refresh, and retest both true and false branches. Capture the exact URL/version used in a bug report.

If a rule still fails, reduce it to one statement and one action, retest, then add statements back one at a time. Record the source value, expected action, actual action, browser, and whether the form was previewed or published.