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

Closed
opened 2026-03-02 02:19:16 +03:00 by kerem · 3 comments
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:

  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.

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-02 02:19:16 +03:00
  • closed this issue
  • added the
    bug
    label
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

<!-- gh-comment-id:1432802655 --> @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
Author
Owner

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

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

<!-- gh-comment-id:1444547674 --> @herzkerl commented on GitHub (Feb 24, 2023): Worked for me after running ‚Server Maintenance > Remove Orphaned Tasks‘.
Author
Owner

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

Closing, post if it's still a problem

<!-- gh-comment-id:1444579897 --> @silversword411 commented on GitHub (Feb 24, 2023): Closing, post if it's still a problem
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#820
No description provided.