[GH-ISSUE #1319] Tasks won't be recreated #2766

New issue

Closed

opened 2026-03-14 05:24:32 +03:00 by kerem · 3 comments

kerem commented

2026-03-14 05:24:32 +03:00

Owner

Originally created by @emtek-at on GitHub (Oct 13, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1319

Server Info:

OS: Ubuntu 20.04
Browser: chrome
RMM Version: v0.15.0

Installation Method:

Standard
Docker

Agent Info:

Agent version: v2.4.0
Agent OS: Win 10 v21H2

Describe the bug
Tasks from Automation Policies won't be recreated if the Policy changes and later get switched back.

To Reproduce
Steps to reproduce the behavior:

Create a Automation Policy with one task
Assign this Policy to a client or site
The Task is getting created on the Agents
Right Click on one Agent ->Assign Automation Policy and activate "Block policy inheritance" -> Submit
The Task is now deleted from the Web UI
Select from the Menue Tools -> Server Maintenance -> Remove Orphaned Tasks. The Task is now deleted from the Client
Right Click on one Agent ->Assign Automation Policy and deactivate "Block policy inheritance" -> Submit
The Task is now in Sync Status "Synced with agent" but it is not created on the Client. The Windows Scheduled Tasks UI doesn't show the Task

Expected behavior
After Step 7 the Task should be recreated on the Client.
I think the "Remove Orphand Tasks" Function does not reset the Status of the Task in the Database.

Additional context
Maybe the Agent should whenever the Tasks get modified check if all Tasks are properly created.

Originally created by @emtek-at on GitHub (Oct 13, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1319 **Server Info:** - OS: Ubuntu 20.04 - Browser: chrome - RMM Version: v0.15.0 **Installation Method:** - [X] Standard - [ ] Docker **Agent Info:** - Agent version: v2.4.0 - Agent OS: Win 10 v21H2 **Describe the bug** Tasks from Automation Policies won't be recreated if the Policy changes and later get switched back. **To Reproduce** Steps to reproduce the behavior: 1. Create a Automation Policy with one task 2. Assign this Policy to a client or site 3. The Task is getting created on the Agents 4. Right Click on one Agent ->Assign Automation Policy and activate "Block policy inheritance" -> Submit 5. The Task is now deleted from the Web UI 6. Select from the Menue Tools -> Server Maintenance -> Remove Orphaned Tasks. The Task is now deleted from the Client 7. Right Click on one Agent ->Assign Automation Policy and deactivate "Block policy inheritance" -> Submit 8. The Task is now in Sync Status "Synced with agent" but it is not created on the Client. The Windows Scheduled Tasks UI doesn't show the Task **Expected behavior** After Step 7 the Task should be recreated on the Client. I think the "Remove Orphand Tasks" Function does not reset the Status of the Task in the Database. **Additional context** Maybe the Agent should whenever the Tasks get modified check if all Tasks are properly created.

kerem

2026-03-14 05:24:32 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 05:24:48 +03:00

Author

Owner

@wangshiok commented on GitHub (Feb 16, 2023):

I think this is been fixed, in my case, you just have to be patient, eventually, the new task will be synced

@wangshiok commented on GitHub (Feb 16, 2023): I think this is been fixed, in my case, you just have to be patient, eventually, the new task will be synced

kerem commented

2026-03-14 05:24:53 +03:00

Author

Owner

@herzkerl commented on GitHub (Feb 24, 2023):

Worked for me after running ‚Server Maintenance > Remove Orphaned Tasks‘.

@herzkerl commented on GitHub (Feb 24, 2023): Worked for me after running ‚Server Maintenance > Remove Orphaned Tasks‘.

kerem commented

2026-03-14 05:24:58 +03:00

Author

Owner

@silversword411 commented on GitHub (Feb 24, 2023):

Closing, post if it's still a problem

@silversword411 commented on GitHub (Feb 24, 2023): Closing, post if it's still a problem