I recently upgraded to ROSv7 (long-term channel, v7.20.8). A script that had run forever under ROSv6 without errors now frequently throws this error: 2026-02-26 15:40:42 fetch,info Download from checkip.dyn.com FAILED: Idle timeout - waiting data 2026-02-26 15:40:43 script,error executing script …

What @rextended meant was probably this: Normally on the forum, in order for other members to be able to give assistance, and to avoid wasting time due to guessing, it's expected that some configuration export (with sensitive information redacted), as well network schema in some cases (this probabl…

I thought that in my original post I had implied that the syntax of the /tool fetch command in the script was effectively identical to that of the sample interactive command that I gave in that post. Having received rextended’s criticism I did provide that line from the script. Have I still failed…

The configuration export is the output of /export hide-sensitive file=myconfig. See this thread: [image] Forum rules Beginner Basics If you are new here - welcome! For your first question, please provide a clear description of your setup, make sure you are run…

Thank you @CGGXANNX . The script isn’t run by netwatch; it’s run by the system scheduler. “netwatch” only came up due to referencing the need for the ftp permission for fetch in ROSv7 from the linked thread (which, when I pasted the link in, I had not expected the forum software to replace the link…

[image] libove: /tool fetch url=" http://checkip.dyn.com/ " output=file dst-path="/dyndns.checkip.html" idle-timeout=15 Or work the other way round: try the above in command line. then try putting that line (and that line only) inside a script and run the script, giving it the appropriate per…

[image] libove: If, as a result, people don’t want to help, so be it. I'm sorry, but you can't blame people for not wanting to help, it's your own fault for being completely uncooperative. I already pointed out in my second post that if you don't show the script, no one can't understand the …

It isn't at all implausible (at least in my mind) that an idle timeout actually occurs. Maybe something isn't ready. This has happened to me, and I had to rewrite the script to tolerate it. Officially the scheduler waits for 5s at system startup, but I seem to recall that it's only documented for o…

Thank you @jaclaz , yes, I’ve done that. … Of, FFS. I’d done that - repeatedly, over a few days. And, until this morning, I’d never gotten anything but an instant success. Today, I do occasionally get timeouts doing it manually. Apologies to all for the wasted time - it appears to be just the dy…

Out of sheer curiosity, I did try (on a normal browser) that site, and also here it seems laggy/slow intermittently, still I wouldn't say that it is 15 seconds laggy (the default should be 10 seconds, which is already plenty to get a few bytes). Are you sure-sure that idle-timeout=15 means actually…

Yes, the idle-timeout is in seconds. In my testing, the fetch either works within 1-2 seconds, or it doesn’t work at all. I’ve removed the idle-timeout now, since the default of 10s is more than sufficient. I’ve also enhanced the script to loop over the fetch command up to 5 times before giving up…

Fetch often times out in script, never at command line, and not when I enable fetch logging

RouterOS Scripting

rextended February 27, 2026, 5:41pm 19

A topic worth taking as a reference, you can see how it ended in the end...