This is a great feature and will remove rubbish schedulers. I know This can be avoided by writing a command line in last, but this will be better.
Yeah that would be very handy to simplify logic. +1
Good idea. It let you “queue” some action simply…
Now you can always have the last action of schedule script to remove itself. But this is a bit trickier…as there is NO “this” variable to know what script you’re in (/system/scheduler/remove [find name=“$name”] will NOT work)…so you need to store the scheduled script name inside (i.e. /system/scheduler/remove [find name=“XXXX”]).
- I believe a simple solution, like adding a checkbox or an option within the interval box, would greatly streamline this process and enhance user experience.
- I know that a final line can be added that remove the schedule, but what if the schedule name is changed later before execution?
Please don’t be negative. If you like this topic/post, leave a comment u[/u].
In this case comment can be used to identify such scheduler, or simply adjust code in scheduler when renaming it. When changing something one must be aware on what some change is affecting.
I hate this deja-vu feeling I have… 
No, wait 
:
https://forum.mikrotik.com/viewtopic.php?t=213043
Repetita iuvant …
https://en.wikipedia.org/wiki/List_of_Latin_phrases_(R)
And it can be related to this http://forum.mikrotik.com/t/feature-request-run-after-reboot/183965/1 
The last thing that helps OP’s cause is cross-posting, which is not allowed on the forum.
I’d recommend you file as a Feature Request at help.mikrotik.com - to which MikroTik likely say some form of: “thanks … if we get more requests, we may look at it”.
But never know. Certainly having any “+1” comments spread across TWO posting isn’t going to help anyone.
(topics merged)