[GH-ISSUE #2329] [BUG] ALL tasks firing randomly #3384

New issue

Open

opened 2026-03-14 07:14:35 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 07:14:35 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2329

Describe the bug
For some unknown reasons manual tasks are run randomly on subset of devices per batches.
After investigation the issue does not come from TRMM directly but the way the TRMM agent configure the tasks on windows side.
the tasks are deployed with a trigger (not needed from my point of view but maybe windows requires it) and ** /!\ the option to run if a missed trigger is detected /!\ **
this setup is causing windows to just fire the tasks if for some unknown reasons the tasks is detected as missed.

we have noticed this behavior on multiple batches of devices going all at once and the log in the tasks history of windows is confirming it

Le Planificateur de tâches n’a pas pu lancer la tâche « \TacticalRMM_JInxbhZoHHjunUvljZVuGbZuFLasjUlJuMM » comme prévu. L'instance « {e143f970-98fd-465f-8539-4861d24cb5a9} » 

démarre maintenant comme demandé par l’option de configuration pour exécuter la tâche lorsqu’elle sera disponible, si la planification n’est pas exécutée.

To Reproduce
no entirely sure how to reproduce but the conclusion seems correct.

Expected behavior
not have random tasks firing

Screenshots

Originally created by @P6g9YHK6 on GitHub (Oct 27, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2329 **Describe the bug** For some unknown reasons manual tasks are run randomly on subset of devices per batches. After investigation the issue does not come from TRMM directly but the way the TRMM agent configure the tasks on windows side. **the tasks are deployed with a trigger** (not needed from my point of view but maybe windows requires it) and ** /!\ the option to run if a missed trigger is detected /!\ ** this setup is causing windows to just fire the tasks if for some unknown reasons the tasks is detected as missed. we have noticed this behavior on multiple batches of devices going all at once and the log in the tasks history of windows is confirming it ``` Le Planificateur de tâches n’a pas pu lancer la tâche « \TacticalRMM_JInxbhZoHHjunUvljZVuGbZuFLasjUlJuMM » comme prévu. L'instance « {e143f970-98fd-465f-8539-4861d24cb5a9} » démarre maintenant comme demandé par l’option de configuration pour exécuter la tâche lorsqu’elle sera disponible, si la planification n’est pas exécutée. ``` **To Reproduce** no entirely sure how to reproduce but the conclusion seems correct. **Expected behavior** not have random tasks firing **Screenshots** <img width="734" height="554" alt="Image" src="https://github.com/user-attachments/assets/a55e87cf-3ce6-4798-af30-0aa8cdd1175f" /> <img width="729" height="553" alt="Image" src="https://github.com/user-attachments/assets/832be929-c17a-44d0-9051-79c4d7f78ef5" /> <img width="1003" height="27" alt="Image" src="https://github.com/user-attachments/assets/5a715f8e-ba53-456b-bad0-b37db2db125d" />

kerem commented

2026-03-14 07:14:41 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Oct 27, 2025):

if this was implemented https://github.com/amidaware/tacticalrmm/issues/2084 i would not have spent 1 hours thinking it was a users fault.

@P6g9YHK6 commented on GitHub (Oct 27, 2025): if this was implemented https://github.com/amidaware/tacticalrmm/issues/2084 i would not have spent 1 hours thinking it was a users fault.

kerem commented

2026-03-14 07:14:46 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Nov 4, 2025):

updated the title it's all tasks firing randomly not only manual

@P6g9YHK6 commented on GitHub (Nov 4, 2025): updated the title it's all tasks firing randomly not only manual