TinyTask Schedule Tasks: Run Macros Automatically at Set Times

No. TinyTask does not include any scheduling feature. It can record, play, loop, and compile macros, but it has no option to run a macro at a specific time. To schedule macros, you need to compile the recording to an EXE file and then use Windows Task Scheduler to launch the EXE at your desired time.

This two-step approach actually gives you more scheduling flexibility than a built-in scheduler would. Windows Task Scheduler supports daily, weekly, monthly, at-login, on-idle, and event-based triggers, along with options for repeating intervals, delays, and conditions.

Not directly. A .rec file is a data file, not an executable program. Task Scheduler needs a program to launch. However, you can work around this by scheduling TinyTask itself with the .rec file as a parameter. Create a batch script that opens TinyTask, loads the .rec file, and sends the Play hotkey using a tool like AutoHotkey.

This workaround is more fragile than compiling to EXE. The compiled approach is recommended because the EXE is self-contained, starts instantly, and does not depend on TinyTask being installed or configured correctly.

No. TinyTask macros send mouse clicks and keyboard events to the active desktop. When Windows is locked, there is no active desktop to receive these events. The macro will either fail silently or click on lock screen elements, which is not what you want.

To prevent this, configure your power settings to never lock the screen during scheduled macro hours. Go to Settings > System > Power > Screen timeout and set it to Never. If security is a concern, set the screen to lock after the macro’s expected completion time. Alternatively, use a keep-alive tool that prevents Windows from locking.

In Task Scheduler, edit the trigger for your task. Check the box “Repeat task every” and set the interval to 1 hour. Then set “for a duration of” to the total period you want it active (e.g., 8 hours for a workday, or “Indefinitely” to repeat all day). The macro will run once per hour at the same minute offset from the initial trigger time.

Make sure each run of the macro finishes before the next one starts. If your macro takes 2 minutes to complete, an hourly schedule has no issues. But if it takes 45 minutes, you need at least a 1-hour gap. Set “Stop the task if it runs longer than” in the Settings tab as a safety measure.

Yes. Create a batch script (.bat file) that runs multiple compiled EXE files in order with start /wait commands and timeout delays between them. Point Task Scheduler at the batch file instead of an individual EXE.

The start /wait command tells Windows to wait until the current EXE finishes before moving to the next line. The timeout command adds a pause in seconds to let apps respond between macro steps. This is the most reliable way to run complex multi-step automation sequences on a schedule.

TinyTask records absolute pixel coordinates. If anything about your screen setup changes between recording and playback, the clicks will land in the wrong position. Common causes include: display resolution changed, DPI scaling changed (100% vs 125% vs 150%), monitor arrangement changed in a multi-monitor setup, or the target application window is at a different position or size.

Fix this by recording the macro at the exact same resolution, scaling, and window arrangement that will be active when the schedule triggers. If your macro starts by pressing Win+D (show desktop) and then opens the target app fresh, it will be more consistent than assuming the app is already in the right position.

Yes. A virtual machine provides a consistent, isolated environment where resolution and window positions never change unexpectedly. This makes scheduled macros more reliable than running them on a physical machine where settings may drift over time.

Set up the VM at a fixed resolution (e.g., 1920×1080), disable screen lock and screensaver inside the VM, install the required apps, and record your macro there. Task Scheduler inside the VM can then run the compiled EXE on schedule. The VM does not need to be in fullscreen mode on the host, but it must have an active session.

If a scheduled macro is running and clicking in the wrong places, press Ctrl+Alt+Delete to interrupt it. This opens the Windows security screen, which takes focus away from the macro. Then open Task Manager and end the macro’s EXE process. To prevent the macro from running again, open Task Scheduler, find the task, right-click it, and select Disable.

As a preventive measure, always set “Stop the task if it runs longer than” to a reasonable duration in the task’s Settings tab. For a macro that should take 1 minute, set the limit to 5 minutes. This automatically kills the process if something goes wrong.

Yes. Task Scheduler works identically on Windows 10 and Windows 11. The interface, features, and configuration options are the same. The steps in this guide apply to both versions. Task Scheduler has also been available since Windows XP, though older versions have fewer trigger options and less granular settings.

One minor difference: Windows 11 sometimes moves the Task Scheduler entry in the Start Menu search results. If you cannot find it by searching, press Win+R, type taskschd.msc, and press Enter. This direct command works on all Windows versions.

For most users, Windows Task Scheduler combined with TinyTask compiled EXEs is the simplest and most reliable approach. It requires no additional software and integrates directly with Windows. However, if you need more advanced features, there are alternatives.

Power Automate Desktop (free from Microsoft) can trigger flows on schedules and includes built-in UI automation that does not rely on pixel coordinates. AutoHotkey scripts can be scheduled via Task Scheduler with more flexibility than TinyTask EXEs, including the ability to find windows by title rather than position. For enterprise-level scheduling, tools like UiPath or Automation Anywhere provide robust scheduling, error handling, and logging, but they are significantly more complex to set up.