First, you need to understand that this solution will not work for the same scenario as it is often used in Cisco equipment!
In Cisco, any config you have not explicitly saved will be lost when you reboot and the router comes back in the state that was last saved.
However, in MikroTik this is not the case! Everything you configure is immediately committed to flash memory, and a reboot will bring back the same config you last made.
So when you want to do this to guard against config mistakes that lock you out, it will not work.
However, MikroTik has another feature for that: safe mode. When you enable safe mode and then make config changes, and you lose your connection, all changes are rolled back to the moment you enabled safe mode. When you end safe mode yourself, all changes are committed and will remain in place.

So please study that before trying your reboot-in-5-minutes solution which will not work as you expect.
Other than that, I usually have a job in the system scheduler to to a reboot once at some specified time, and e.g. when I want to update RouterOS I only download it and then set the time for the reboot the next night e.g. at 01:00 or 03:00 and it will reboot and install the update at that time. That works fine.

The scheduler is the advised way to do that. Just enter a one-time (00:00:00 repetition interval) job and set the correct time for it to run.
I have a job like this in the scheduler at all times:

Code: Select all

/system scheduler
add name=scheduled_reboot on-event="/system reboot" policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-date=jul/30/2020 start-time=01:01:01

When I need to schedule a reboot I just set the time and date and it runs.

interface goes down and I loss acces to router.
Only router reboot takes the interface back again