Summary: A new rate shop rule with no stop criteria can loop, asking for rates over and over. It can slow everything down and look like an outage. Add a criterion so the rule does not fire again on its own rate result.
Problem
After you add a new rate shop business rule, shipping slows to a crawl or looks like a full outage: even the web page is slow. The same loop can also show up as one shipment that spins and never finishes when you scan to process.
Cause
The rate shop rule re-fires on the result of its own rate request, so it loops (request, response, request, and so on) and uses up resources until throughput collapses. The rule needs a criterion that stops it from firing again on a shipment it already rate shopped.
How to check: compare when the slowdown started to when a rate shop rule was last added or changed.
Fix
- Find the rate shop rule that was added or changed around the time the slowdown started.
- Open the rule's criteria.
- Add a criterion that stops the rule from running again on a shipment it already processed, so it fires once per shipment.
- Save, then confirm shipments flow again.
- Add the same guard to any other rate shop rule that is missing it.
What you should see
Shipments process normally again, the web page is responsive, and you no longer see repeated rate requests for the same shipment.
Related articles
- Keep one customer off a carrier using a rate shop rule
- Rate markup or rate shop not applied: fix the rule Event