routing filter with bgp-as-path match to set-bgp-local-pref

Goal: I don’t want to prefer my cogent upstream for routes to china telecom / china unicom ( AS4134, 4837) via as 701 by setting the local-pref to 90.

Based on what I’ve read this should do it:

/routing filter
chain=cogent-in bgp-as-path=174,701,4837 invert-match=no action=accept set-bgp-local-pref=90 set-bgp-prepend-path=“”
chain=cogent-in bgp-as-path=174,701,4134 invert-match=no action=accept set-bgp-local-pref=90 set-bgp-prepend-path=“”
chain=cogent-in invert-match=no action=jump jump-target=bgp-in set-bgp-prepend-path=“”

However, this has no impact on a prefix that matches, ie:

/ip route print detail where dst-address=“183.0.0.0/10”
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
0 ADb dst-address=183.0.0.0/10 gateway=xx gateway-status=xx reachable via sfp1 distance=20 scope=40 target-scope=10 bgp-as-path=“174,701,4134” bgp-med=2020 bgp-origin=igp bgp-communities=174:21000,174:22013
received-from=cogent4

In fact, I can’t see the bgp local pref in route print detail and it isn’t being used. I feel like I’m missing something basic.

Edit: I am blind, there was a typo. This does in fact work as expected!