Undocumented feature (bug?) in script scheduler

RouterOS General
1

Hello

I was trying to schedule the execution of a script each day at 12:00:00. The name of the script was “disableNigthSurfing”. The script was never executed, because its name is starting with the string “disable”, which is probably the internal way to store a disabled rule.

When I changed the name of this script into “DenyNightSurfing”, everything started to work fine. I lost near to a week to find out what was wrong. :frowning:

I will not be the only one who is going to have that problem, so I suppose we will have to change this behaviour (better) or to mention this limitation in the manual (worse).

According to the reactions on this post, I could file this as a bug.

Kind regards.

2

Works for me:

/system script
add name=“disableTest” source=
“/log info test”
/system scheduler
add interval=30s on-event=“disableTest”

/log print
14:00:26 script,info test
14:00:56 script,info test

3

It is case sensitive, so maybe you had written “DisableNigthSurfing” in the scheduler?
Without actually seeing the errored setup it is hard to know what happened.