Adding filter next-ip action as follows causes the evo-aftmand daemon to crash and logs are observed. The observed logs are in symptoms section.

[edit firewall family inet filter SP_tunnels]

term 1 {
from {
source-address {
<ip-address>;
}
protocol udp;
source-port 4092;
}
then {
next-ip <ip-address>;  <<<<<<<
}
}

This issue might be seen if the following conditions are met:
* On Junos Evolved PTX platforms
* Configuring next-IP/next-IPv6 action for a filter

You can see the below logs when configuring filter next-ip action

Nov 23 08:46:02.144 router-name evo-aftmand-bt[832]: [t:832] [Error] RT-NOTIF : Failed to add request for req: proto: ipv4 prefix: <ip prefix> app-id: 1

Nov 23 08:46:02.145 router-name evo-aftmand-bt[832]: [t:832] [Error] Dfw: Failure in RtNotif StartListening

Nov 23 08:46:02.145 router-name evo-aftmand-bt[832]: [t:832] [Error] PBR: virtual int EalPolicyRouteHandler::onAdd(Adapter*)Failed to add PolicyRoute object from PIL Handler callback policy route type:2 key value:FwPolicyRoute:nextIpv4:Prefix(Type=IPV4 bytes=[ ] length=32) mask=[ ] _ri_default_family_2

Nov 23 08:46:02.193 router-name evo-aftmand-bt[832]: [t:1115] [Error] Jexpr: Initialization of token actions failed for filter:SP_tunnels

Upgrade to following releases.

23.4R2-S2-EVO

24.3R1-EVO

24.2R2-EVO

24.4R1-EVO