Hello, This is a general issue I've noticed in rOS7, regardless of specific version, including latest 7.23. While sometimes having similar issues in rOS6, it's generally more robust. We have multiple systems routing services that usually have ~200k+ connections. Some times some of these, like SIP…

Hi rextended, I know that [find] will first build a list of connections matching the find filter, then, if some expire while the command is running, it will fail. However the issue here is that it fails while printing too : [sin3vil@MASTER] > ip firewall/connection/print where reply-src-address=1…

If some connection are closed (removed) between the start and the end of the command, it do error and stop working, leaving open some connections. Because those close automatically in 60 seconds... and I care about closing the older ones... So if the script finishes within a minute, it doesn't…

Thanks for pointing that out. This machine generally serves UDP connections, so I haven't actually checked TCP settings.

@rextended what about do { } on-error={} failing in this context? Any theories?

I don't use them; for me, using them is a programming failure. I really need to be forced to use them (like :resolve).

The proper method (and why it's needed), together with other methods are discussed in this thread: [image] How to flush connection in a failover route change ? General I get the (vague?) impression that you think I like writing poetry and only by insinuation p…

Yeah, the surely compatible version, as discussed in the thread, foreach var in=$someArray do={ do { $something } on-error={ $somethingElse } } does not work here, at least in rOS7. on-error doesn't seem capable of eating the error and continuing the loop.

What you wrote matches neither anserk's or my syntax. As discussed there, only the first (my) version is officially documented. (I would expect both to work.)

You said discussed in this thread, so I assumed you meant all posts. This form is the one that yearly7100 says works in both rOS6 and rOS7 and isn't for and foreach specific. The for/foreach specific error handling is not really applicable here as the find itself seems to fail : [sin3vil@MASTER] >…

I think you missed the whole point: find gives you a static result set of internal ids. In the meantime any of these connections in your result set could timeout, meaning they vanish while you're looping over the result set. that's why where timeout>60 is in the sample. and if removing/iterating you…

"No such items" when taking any action under /ip firewall connection in rOS7

RouterOS Scripting

lurker888 May 27, 2026, 5:56pm 9

The proper method (and why it's needed), together with other methods are discussed in this thread: