In an EVPN multihomed active-active scenario, when LACP is enabled on PE-CE child member links, LACP force-up feature should not be enabled in conjunction with EVPN core isolation feature (enabled by default) because it is currently not supported in this scenario as these two features are contradictory in terms of action they take.

When "lacp force-up" knob is configured on ae interface and the core is isolated in EVPN-VXLAN scenario, the force-up is getting precedence over core-isolation. This results in a traffic drop which is destined to the core.
Sample configuration:
user@host> set groups xxx interfaces aex aggregated-ether-options lacp force-up

Use the below CLI command to check lacp intefaces
user@host> show lacp interface

This has been resolved  in later releases, on where Core-isolation takes precedence over force-up: https://prsearch.juniper.net/problemreport/PR1733543,

Resolved-In

evo:22.4R3-EVO

evo:23.1R2-EVO

evo:23.2R2-EVO

evo:23.3R1-EVO

evo:23.4R1-EVO

junos:22.2R3-S2

junos:22.3R3-S1

junos:22.4R3

junos:23.1R2

junos:23.2R1-S1

junos:23.2R2

junos:23.3R1

junos:23.4R1