Two routing editors can make it unclear which rule will be saved. Preserve the configuration and verify recipients after the display fix.
Quick answer
Gravity Flow 3.1.1 fixes a Firefox display issue where a legacy conditional-routing interface can appear beneath the current email-notification controls. Preserve the saved rule, update the plugin, and load fresh admin assets before editing again. Then test the recipients with synthetic entries. Two visible editors do not prove two notifications were sent, and one visible editor does not prove the stored rule is correct.
Preserve the rule before touching either editor
Capture the notification name, enabled state, recipients, conditional operators, and all-versus-any setting. Export the form or workflow through supported tools and keep a redacted screenshot of both control sets. Do not delete the lower block merely because it looks old: a display problem can make it unclear which control is connected to the saved configuration.
If the page contains unsaved work, preserve a readable record of the intended changes before reloading. Ask other administrators to avoid editing the same notification during the investigation. Concurrent saves can produce a genuine configuration conflict that becomes difficult to distinguish from the Firefox-specific interface defect.
Separate a browser artifact from stored data
Open the same saved notification in a clean Firefox session and in a second supported browser. Compare the visible control count and the rule values before making an edit. Browser extensions, stale resources, custom admin CSS, and duplicate scripts are useful additional checks when the behavior persists, but none should be assumed to be the cause without evidence.
Record the Gravity Flow version and inspect whether the admin resources correspond to the deployed package. An update followed by stale JavaScript can leave the old editor behavior visible. Refresh through the supported cache controls and reload the admin screen. Avoid clearing unrelated customer-facing caches unless the evidence shows those layers also serve the affected admin assets.
Illustrative diagnostic worksheet. Values are examples, not measurements from a customer site.
Save one controlled rule change
On staging, use two internal test recipients and a synthetic field with two choices. Record the initial routing rule, change one condition, save once, and reopen the notification in a fresh request. Compare operators, values, recipient addresses, and enabled state. This checks persistence without depending on whichever controls remain visible in the original tab.
Repeat in Firefox and the comparison browser using the same configuration. When a mismatch appears, stop before sending a large batch of entries. Capture the save request timing and resulting stored configuration. Do not copy session cookies, authorization headers, or recipient personal data into a public support discussion.
Prove the delivery rule with branch tests
Submit a marked entry for each valid condition and one that matches neither. Record the expected recipient before submission, then compare the workflow history, mail log, and approved test inbox. Count provider-accepted messages separately from retries shown in a local log. A local resend attempt is not automatically a second delivered email.
Test blank and unexpected values when they are reachable through the real form. If routing uses a Role field, inspect the separate empty-role notification issue covered by the release notes. Keep that recipient-scope problem separate from this editor-display defect. The Firefox fix should make editing dependable; the branch tests establish that the intended people receive the right entry.
What if duplicate controls remain after updating?
Provide support with the plugin versions, Firefox version, a minimal form export, the affected notification screen, and whether the issue occurs in a clean session. Include the comparison-browser result and whether saving changes the stored rule. Keep production on the last verified configuration while the interface is investigated. If a message went to the wrong audience, follow the site owner incident process based on actual delivery evidence.
Working example
Use this as a read-only starting point or an evidence worksheet. Replace example identifiers with the approved staging fixture.
routing_fixture:
browser: Firefox
notification: reviewer-alert
condition: synthetic-choice-A
expected_recipient: internal-test-A
saved_rule: compare-before-after
delivered_count: record-observed
Before closing the work
- Only the intended routing editor is visible.
- Saved operators and recipients remain intact.
- Each test entry reaches the expected mailbox.
- No duplicate request or email is introduced.
For help applying these checks to a live site, HandL WP WordPress support can review the affected configuration and verify the result. Continue with Gravity Flow routing field audit when that adjacent issue matches your evidence.
Helpful references