The Move Flows action now offers greater flexibility for managing traffic, maintaining performance, and enforcing SLA requirements. With the addition of the App/Network SLA Rule Type, you can use Move Flows to better control traffic.

Previously, the action only excluded SLA violating paths for new flows, leaving existing flows unchanged and relying on Link Quality and Application Metrics unless the field was empty. Now, you can choose between Move Flows Graceful and Move Flows Forced for more control:

• Move Flows Graceful moves existing flows and excludes paths for new flows that violate SLAs, considering Link Quality and Probe Metrics.
• Move Flows Forced actively shifts flows from non-performing paths to better ones, even across NAT boundaries, using Link Quality and Application/Probe Metrics.

Move Flows Forced triggers on events such as WAN interface changes, link degradation, app unreachability, probe failures, or path revalidation. It supports various path types, including private/public VPNs, Direct Internet, and enterprise VPNs, across active and backup configurations.

Additionally, the action supports a wide range of path types, including Private L2, Direct (Public/Private), SD-WAN VPNs (Public/Private), and Third-Party VPNs (Public/Private). It works across combinations of active and backup paths like Direct Internet, Direct Private, Public/Private VPN, Standard VPN, and enterprise VPN configurations.