[GH-ISSUE #2355] My Windows computer isn't running tasks with past dates #3398

New issue

Open

opened 2026-03-14 07:16:05 +03:00 by kerem · 3 comments

kerem commented

2026-03-14 07:16:05 +03:00

Owner

Originally created by @lergolas on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2355

Hello everyone.

I'm having trouble creating tasks if the computer isn't available at that moment.

For example, I create a one-time task and assign it to a computer that's currently offline.

According to the documentation, when you create a task to run only once, with a past date, it's created to run 5 minutes later. But that's not the case. The task is created at the time I specified when creating it in TRMM, and it doesn't run.

This is what the documentation says:
Run Once:

For future dates, tasks run as scheduled.
For past dates, tasks are created to run 5 minutes after being registered with the Windows Task Scheduler. This ensures the task runs at least once, as the scheduler will not execute tasks with past "Run Once" dates.

What am I doing wrong?

Thank you very much.

Originally created by @lergolas on GitHub (Nov 21, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2355 Hello everyone. I'm having trouble creating tasks if the computer isn't available at that moment. For example, I create a one-time task and assign it to a computer that's currently offline. According to the documentation, when you create a task to run only once, with a past date, it's created to run 5 minutes later. But that's not the case. The task is created at the time I specified when creating it in TRMM, and it doesn't run. This is what the documentation says: Run Once: - For future dates, tasks run as scheduled. - For past dates, tasks are created to run 5 minutes after being registered with the Windows Task Scheduler. This ensures the task runs at least once, as the scheduler will not execute tasks with past "Run Once" dates. What am I doing wrong? Thank you very much.

kerem commented

2026-03-14 07:16:12 +03:00

Author

Owner

@jt-looma commented on GitHub (Dec 8, 2025):

Hello,

just wanted to add that we've noticed the same thing on our end in the last few months. And even after trying to recreate the tasks and everything we didn't manage to get it to work.

What we've noticed is that only tasks that were configured to run once have this problem. Repeated tasks (for example daily) run without problems as do onboarding tasks.
The tasks configured to run once only run on devices that are online at the time set for the execution of the task. All the devices that are offline at that time never run those tasks and stay in the "synced with agent" and "awaiting output" statuses, even though the "Run ASAP after scheduled start is missed" checkbox is checked.
Running one of those missed tasks via right-click "Run task now" works without problem, but checking every device one by one and running missed tasks manually isn't really a feasible option.

We've had this problem in version 1.2.0 and in version 1.3.1 it still persists.

The screenshot shows how it looks on our end (don't mind the black and white boxes those are there for censoring reasons). Even though the device is online the tasks configured to run once don't run automatically.

@jt-looma commented on GitHub (Dec 8, 2025): Hello, just wanted to add that we've noticed the same thing on our end in the last few months. And even after trying to recreate the tasks and everything we didn't manage to get it to work. What we've noticed is that only tasks that were configured to run once have this problem. Repeated tasks (for example daily) run without problems as do onboarding tasks. The tasks configured to run once only run on devices that are online at the time set for the execution of the task. All the devices that are offline at that time never run those tasks and stay in the "synced with agent" and "awaiting output" statuses, even though the "Run ASAP after scheduled start is missed" checkbox is checked. Running one of those missed tasks via right-click "Run task now" works without problem, but checking every device one by one and running missed tasks manually isn't really a feasible option. We've had this problem in version 1.2.0 and in version 1.3.1 it still persists. The screenshot shows how it looks on our end (don't mind the black and white boxes those are there for censoring reasons). Even though the device is online the tasks configured to run once don't run automatically. <img width="1621" height="418" alt="Image" src="https://github.com/user-attachments/assets/f9266b8d-00c9-4773-9406-2a5fe37fdecb" />

kerem commented

2026-03-14 07:16:17 +03:00

Author

Owner

@silversword411 commented on GitHub (Dec 8, 2025):

There are known quirks with the current "tasks" implementation and how it interacts with the windows task scheduler. There's multiple other issues regarding this.

It's planned to completely replace, and internalize tasks to the TRMM servers scheduler so this should resolve when that is completed.

@silversword411 commented on GitHub (Dec 8, 2025): There are known quirks with the current "tasks" implementation and how it interacts with the windows task scheduler. There's multiple other issues regarding this. It's planned to completely replace, and internalize tasks to the TRMM servers scheduler so this should resolve when that is completed.

kerem commented

2026-03-14 07:16:22 +03:00

Author

Owner

@Taomyn commented on GitHub (Jan 29, 2026):

Hi, I've only recently set up TRMM v1.4.0 on a clean Debian 12 server, and hit this issue where run-once tasks are not running when the Windows agent comes on-line, as the workstation was shutdown. As mentioned above, once the machine is on-line I can manually use run task now, and it works. The agent shows as sync'd and everything else seems to check out - I can run the Windows agent with logging and don't see any errors but plenty of chatter between it and the server.

Is this still not resolved?

@Taomyn commented on GitHub (Jan 29, 2026): Hi, I've only recently set up TRMM v1.4.0 on a clean Debian 12 server, and hit this issue where run-once tasks are not running when the Windows agent comes on-line, as the workstation was shutdown. As mentioned above, once the machine is on-line I can manually use run task now, and it works. The agent shows as sync'd and everything else seems to check out - I can run the Windows agent with logging and don't see any errors but plenty of chatter between it and the server. Is this still not resolved?