Issue :

Redirect Rule Conflict When Query Term Exists in Multiple Rules - When the same query term is included in more than one configured Redirect rule, customers may see a redirect that is different from what they expect.
 

Environment :

This is expected product behavior and can be seen in all environments (PROD/STG).

Cause :

The system prioritizes redirect rules based on the last changed timestamp. If a query term exist in  multiple rules, the rule with the most recent modification will be applied. 

To make a specific rule effective immediately without deleting it from other rules, the rule needs to be disabled and then re-enabled. This updates its modification timestamp, ensuring it becomes the active rule in subsequent API calls.

 

Example :

• Redirect Rule 1: "xmas | christmas | x mas | christmas shop | xmas shop"  

  • last changed: Oct 22, 2025, 7:07 AM)

• Redirect Rule 2: "christmas" (expected to take effect) 

  • last changed: Oct 09, 2025, 1:28 PM)

• In this case, the term "christmas" exists in both rules. Rule 1 is currently applied because it has the latest timestamp. However, the customer expected Rule 2 to take effect.

Resolution :

1. Disable Redirect Rule 2.
2. Re-enable Redirect Rule 2.

This updates its modification timestamp, making Rule 2 the most recently modified rule. As a result, Redirect Rule 2 will take precedence and become effective immediately in all corresponding API calls.

Conclusion:

This behaviour is by design. If a query term exists in multiple redirect rules, the redirect rule with the most recent modification will be applied. To prioritise a specific rule without deleting query terms from other rules, simply disable and re-enable the desired rule so it becomes the latest modified and takes effect immediately.