Issue
Updated or deleted query pipeline rules continue to appear in Fusion query responses even after disabling or deleting them.
Diagnosis
To confirm whether this issue applies:
Verify that the rule has been successfully disabled or deleted in the Rules UI.
Use the Query Workbench or API to observe whether the expected changes (e.g., removed facet rules, set_param adjustments) are taking effect.
Check whether multiple query rewrite collections are associated with the same app in Object Explorer.
Review the query pipeline configuration to see which query rewrite collection is actively in use.
This issue often arises when the Fusion app is connected to multiple collections, leading to rule updates being incorrectly written to or applied from the wrong query rewrite collection.
Environment
Fusion 5.9 and above
Applies to deployments where:
Multiple collections are attached to a single Fusion app
More than one query rewrite collection exists across those collections
Query pipelines are configured to read from or publish to incorrect rewrite collections
Cause
Fusion apps that include multiple collections may reference multiple query rewrite collections. In such cases:
Rules may be published to a different rewrite collection than the one used by the pipeline
Query pipelines may reference stale or unrelated rule data
Changes to rule logic (create, update, delete) may silently apply to a non-active collection
This cross-collection contamination can prevent expected rule changes from reflecting in query responses.
Resolution
Step 1: Verify active rewrite collection in pipeline
Open the Fusion UI and navigate to Query Pipelines.
Select the relevant pipeline.
Under the "Apply Rules" stage, verify the rewrite collection assigned.
Ensure the selected collection is the one that corresponds to your desired ruleset.
Step 2: Review app-to-collection assignments in Object Explorer
Navigate to Object Explorer in the Fusion UI.
Select the affected app.
Review all associated collections listed under the app.
Identify and remove unrelated or legacy collections (especially those with their own rule logic or pipelines).
Select the collection
Click Remove
Confirm that each app is only linked to collections relevant to its intended rule logic and query flows.
Note: If multiple apps require shared access to collections, configure query rewrite collections carefully and ensure no cross-app pollution occurs.
Step 3: Recreate or re-publish rules if necessary
After correcting the app-to-collection assignments:
Recreate any necessary rules in the correct collection.
Re-deploy query pipelines referencing the corrected rewrite collection.
Validate that updated rules now reflect in query responses as expected.