[GH-ISSUE #1928] [BUG] Devices stays in outputs of automation policy even if removed #3146

Open
opened 2026-03-14 06:42:37 +03:00 by kerem · 2 comments
Owner

Originally created by @P6g9YHK6 on GitHub (Jul 24, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1928

Server Info (please complete the following information):

  • OS: [Debian 12
  • Browser: Edge
  • RMM Version (as shown in top left of web UI): 19.2

Installation Method:

  • Standard
  • Standard with --insecure flag at install
  • Docker

Agent Info (please complete the following information):

  • Agent version (as shown in the 'Summary' tab of the agent from web UI): v2.7.0
  • Agent OS: all

Describe the bug
when changing a device to another policy the output of the old policy retains the data of the device that is no longer attached

To Reproduce
Steps to reproduce the behavior:

  1. Go to automation policy
  2. Click on move a device from one policy to another
  3. check the old policy
  4. See error

Expected behavior
the old policy should have the results purged when removed.

Screenshots
image

Originally created by @P6g9YHK6 on GitHub (Jul 24, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1928 **Server Info (please complete the following information):** - OS: [Debian 12 - Browser: Edge - RMM Version (as shown in top left of web UI): 19.2 **Installation Method:** - [X] Standard - [ ] Standard with `--insecure` flag at install - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): v2.7.0 - Agent OS: all **Describe the bug** when changing a device to another policy the output of the old policy retains the data of the device that is no longer attached **To Reproduce** Steps to reproduce the behavior: 1. Go to automation policy 2. Click on move a device from one policy to another 3. check the old policy 4. See error **Expected behavior** the old policy should have the results purged when removed. **Screenshots** ![image](https://github.com/user-attachments/assets/a2ace6c2-26fe-4904-b0f8-804afad9c098)
Author
Owner

@silversword411 commented on GitHub (Jul 28, 2024):

Yes, I've seen this one too

<!-- gh-comment-id:2254628933 --> @silversword411 commented on GitHub (Jul 28, 2024): Yes, I've seen this one too
Author
Owner

@P6g9YHK6 commented on GitHub (Aug 29, 2024):

seens this also for deleted devices.

<!-- gh-comment-id:2317009542 --> @P6g9YHK6 commented on GitHub (Aug 29, 2024): seens this also for deleted devices.
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#3146
No description provided.