There is no scheduler in the program
Open Prefs and look at the whole menu. Speed, loops, hotkeys, appearance. Nothing else.
That is the complete list of what the program can be configured to do. There is no hidden panel and no advanced mode. A scheduler was never part of it.
This is consistent with everything else here. The program is a recorder and a player, kept deliberately small, and a scheduler is a large feature.
Why people think it has one
Because of the downloads labelled as an editor version.
Those files are a different vendor's product, and that product does have a scheduler. Open its Options menu and you find scheduling, triggers and a task manager, none of which exist in the program you were looking for.
So people download something they believe is an advanced version, see a schedule feature, and reasonably assume the feature exists. It does, in that other program. It is not the same software and it is not free in the same way. The with editor page shows both programs side by side so you can tell which one you have open.
Letting Windows do the timing
Three steps, and the first one is the one people skip.
Compile the macro first. Press the .exe button and save the standalone file somewhere permanent, not in your downloads folder. Task Scheduler needs a file that will still be there next week. The compile process, including the speed and loop settings that get written into the file, is on the compile to EXE page.
Create a basic task. Open Task Scheduler from the Start menu, choose to create a basic task, name it, and pick when it should run.
Point the action at your compiled file. Choose to start a program and browse to the file you just built. Nothing goes in the arguments box.
That is it. Windows launches your macro at the time you set, and the macro replays exactly as it would if you had double-clicked it.
The limits you need to know before you rely on this
Read this part before you set anything to run overnight.
It will not work on a locked screen. A macro drives the mouse and keyboard against what is on screen. On a locked or signed-out machine there is nothing there to drive. Set the task to run whether the user is logged on or not and it runs in a session with no desktop, doing nothing useful.
The screen has to look the same as when you recorded. The macro replays positions. A window that opens somewhere else, an update dialog that appeared overnight, a browser that restored a different tab: any of those and the clicks land wrong. This is the biggest reason scheduled macros fail while the same macro works fine by hand.
Nobody is watching it. A macro that misfires at your desk gets stopped in a second. The same macro at three in the morning keeps going. If you have set a repeat count, it repeats the mistake. Loop behaviour is covered on the loops page.
Administrator mismatch still applies. If the application being automated runs elevated and your macro does not, Windows blocks the input between them. The Windows 11 page covers that in full.
Making a scheduled macro survivable
If you are going to do this anyway, these four habits are the difference between it working and it causing a mess.
Have the macro open the application itself. Record the whole thing from a clean desktop, including launching the program. Do not assume a window will already be open and in the right place.
Maximise every window you touch. A maximised window is in a predictable position on any screen. A restored window is not.
Prefer keyboard steps to clicks. Keyboard sequences do not care where anything is on screen, so they survive a layout change that would break a click.
Run it once while you watch. Set the task to trigger a minute from now, sit there, and see what actually happens. Have Pause under a finger, as described on the stop playback page.
Running a macro when you log in
This is a simpler case and it does not need Task Scheduler at all.
Put a shortcut to your compiled macro in the Windows startup folder. It runs after you sign in, when the desktop exists and everything is where it should be. That avoids the locked screen problem completely, because you are present by definition.
Press Win+R, type shell:startup, and drop the shortcut in the folder that opens.
When you have outgrown this
Be honest about what you are building.
Does your scheduled macro need to check whether something worked? Wait for a page to load, retry on failure, or take a different path depending on what it finds? Then you have moved past what a recorder can do. No amount of scheduling fixes that, because the problem is the macro, not the timing.
At that point a scripting tool is the right answer, and switching is cheaper than maintaining a fragile recording. The options are set out on the alternatives page.
Frequently asked questions
No. There is no timer, trigger or calendar in the program. The working TinyTask scheduler is Windows Task Scheduler, launching a compiled copy of your macro.
Compile it to a standalone file with the .exe button, then create a basic task in Windows Task Scheduler that starts that file at the time you want.
Most likely the machine was locked or signed out. A macro needs a live desktop to click on. Set the task to run only when you are logged on, and leave the session unlocked.
No. There is nothing on screen for the macro to interact with. This is a limitation of screen automation in general, not of this program.
Put a shortcut to the compiled file in the startup folder. Press Win+R and type shell:startup to open it.
Because the editor download is a different program from a different company. It is not a more advanced version of this one, and the with editor page shows the difference.
Not usefully. Task Scheduler launches programs, and a recording is a data file. Compile it first, which is covered on the compile to EXE page.