Command find does not work

I have a router RB751U-2HnD. Software version - 5.20. I need to manipulate the routes from the script.
I have the following configuration:

[admin@MikroTik] /ip route> print
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

DST-ADDRESS PREF-SRC GATEWAY DISTANCE

0 A S 8.8.4.4/32 10.10.10.89 1
1 A S ;;; 111
0.0.0.0/0 10.10.10.89 1
2 A S 192.168.7.0/24 192.168.7.1 bridge1 1
3 A S ;;; 222
0.0.0.0/0 94.19.50.65 1
4 A S 192.168.7.0/24 192.168.7.1 bridge1 1
5 A S 212.109.12.45/32 94.19.50.65 1
6 A S ;;; 333
0.0.0.0/0 10.10.10.89 1
7 DS 0.0.0.0/0 94.19.50.65 2
8 ADC 10.10.10.88/30 10.10.10.90 ether2 0
9 ADC 94.19.50.64/26 94.19.50.81 ether1 0
10 ADC 192.168.7.0/24 192.168.7.1 bridge1 0

[admin@MikroTik] /ip route> print detail
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 A S dst-address=8.8.4.4/32 gateway=10.10.10.89
gateway-status=10.10.10.89 reachable via ether2 distance=1 scope=30
target-scope=10 routing-mark=test_channels

1 A S ;;; 111
dst-address=0.0.0.0/0 gateway=10.10.10.89
gateway-status=10.10.10.89 reachable via ether2 distance=1 scope=30
target-scope=10 routing-mark=channel2

2 A S dst-address=192.168.7.0/24 pref-src=192.168.7.1 gateway=bridge1
gateway-status=bridge1 reachable distance=1 scope=10 target-scope=10
routing-mark=channel2

3 A S ;;; 222
dst-address=0.0.0.0/0 gateway=94.19.50.65
gateway-status=94.19.50.65 reachable via ether1 distance=1 scope=30
target-scope=10 routing-mark=channel1

4 A S dst-address=192.168.7.0/24 pref-src=192.168.7.1 gateway=bridge1
gateway-status=bridge1 reachable distance=1 scope=10 target-scope=10
routing-mark=channel1

5 A S dst-address=212.109.12.45/32 gateway=94.19.50.65
gateway-status=94.19.50.65 reachable via ether1 distance=1 scope=30
target-scope=10 routing-mark=channel1

6 A S ;;; 333
dst-address=0.0.0.0/0 gateway=10.10.10.89
gateway-status=10.10.10.89 reachable via ether2 distance=1 scope=30
target-scope=10

7 DS dst-address=0.0.0.0/0 gateway=94.19.50.65
gateway-status=94.19.50.65 reachable via ether1 distance=2 scope=30
target-scope=10 vrf-interface=ether1

8 ADC dst-address=10.10.10.88/30 pref-src=10.10.10.90 gateway=ether2
gateway-status=ether2 reachable distance=0 scope=10

9 ADC dst-address=94.19.50.64/26 pref-src=94.19.50.81 gateway=ether1
gateway-status=ether1 reachable distance=0 scope=10

10 ADC dst-address=192.168.7.0/24 pref-src=192.168.7.1 gateway=bridge1
gateway-status=bridge1 reachable distance=0 scope=10

Checks operation of find command:
[admin@MikroTik] /ip route> :put [find]
*6;*1;*3;*4;*2;*7;*5;*30000001;*40138613;*40138737;*40138857
All right, there are all routes

[admin@MikroTik] /ip route> :put [find comment=“111”]
*1
[admin@MikroTik] /ip route> :put [find comment=“222”]
*4
The filter by comment works

[admin@MikroTik] /ip route> :put [find dst-address=“10.10.10.88/30”]
*40138613
The filter by dst-address with dynamic (connected) routes works

[admin@MikroTik] /ip route> :put [find dst-address=“0.0.0.0/0”]

[admin@MikroTik] /ip route>
Ooops, empty

[admin@MikroTik] /ip route> :put [find dst-address=“8.8.4.4/32”]
*6
Hmmmm, It’s work

[admin@MikroTik] /ip route> :put [find dst-address=“212.109.12.45/32”]

[admin@MikroTik] /ip route>
Empty again.

Can anybody explain this selectivity and the logic of the find?
For example in software version 5.16 there have been similar problems to seek routes. I could find 0.0.0.0/0 but not on other criteria there were similar errors with empty result.

And one more question. What I need to write to the selection criteria for the find command to view only the main table (main)? To view only another table I simple add something like a <routing-mark = “channel1”>. What must I add in find criteria for routes only without mark?

Dmitry

is working for me:

/ip route> :put [find dst-address="0.0.0.0/0"]
*5;*7;*8

or try this

/ip route> :put [find where dst-address="0.0.0.0/0"]
*5;*7;*8

Mikrotik support said:
“It appears to be problem with some specific config option
Thanks, we will try to fix it in next version.”