starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #1177] All checks for a Client disappear #2669

New issue

Closed

opened 2026-03-14 05:01:23 +03:00 by kerem · 5 comments

kerem commented

2026-03-14 05:01:23 +03:00

Owner

Originally created by @bbrendon on GitHub (Jun 16, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1177

Server Info (please complete the following information):

OS: deb 11
Browser: edge
RMM Version 13.4

Installation Method:

[x ] Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI):
Agent OS: [e.g. Win 10 v2004, Server 2012 R2]

Describe the bug
This has happened twice now, both times for the same Client. All Agent "Checks" (server and workstation) disappear for a client. The problem can be resolved by removing the automation policy and then re-applying it. The tasks never vanish, only the checks.

No changes to policies were made recently. This has happened twice in the past week to one particular client. No other client have shown this behavior.

To Reproduce
Not sure how to reproduce it yet.

Expected behavior
Checks stay like good boi.

Originally created by @bbrendon on GitHub (Jun 16, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1177 **Server Info (please complete the following information):** - OS: deb 11 - Browser: edge - RMM Version 13.4 **Installation Method:** - [x ] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): - Agent OS: [e.g. Win 10 v2004, Server 2012 R2] **Describe the bug** This has happened twice now, both times for the same Client. All Agent "Checks" (server and workstation) disappear for a client. The problem can be resolved by removing the automation policy and then re-applying it. The tasks never vanish, only the checks. No changes to policies were made recently. This has happened twice in the past week to one particular client. No other client have shown this behavior. **To Reproduce** Not sure how to reproduce it yet. **Expected behavior** Checks stay like good boi.

kerem

2026-03-14 05:01:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 05:01:39 +03:00

Author

Owner

@silversword411 commented on GitHub (Jun 17, 2022):

If automation policies are applied, and they don't apply to the os, I've seen times where the policy will be there initially, and after an initial agent sync, policies will disappear when not applicable to the os. Maybe there's 1st run policy checks that will hide policies?

@silversword411 commented on GitHub (Jun 17, 2022): If automation policies are applied, and they don't apply to the os, I've seen times where the policy will be there initially, and after an initial agent sync, policies will disappear when not applicable to the os. Maybe there's 1st run policy checks that will hide policies?

kerem commented

2026-03-14 05:01:44 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jun 23, 2022):

this is a bug with the cache. next time it happens from web UI do Tools > Clear Cache and then checks will re-appear

@wh1te909 commented on GitHub (Jun 23, 2022): this is a bug with the cache. next time it happens from web UI do Tools > Clear Cache and then checks will re-appear

kerem commented

2026-03-14 05:01:49 +03:00

Author

Owner

@Zebble commented on GitHub (Jul 25, 2022):

We were having the same issue happen at a site level. I can confirm that using Tools -> Clear Cache fixes the issue. Thanks @wh1te909 !

@Zebble commented on GitHub (Jul 25, 2022): We were having the same issue happen at a site level. I can confirm that using Tools -> Clear Cache fixes the issue. Thanks @wh1te909 !

kerem commented

2026-03-14 05:01:54 +03:00

Author

Owner

@bbrendon commented on GitHub (Jul 29, 2022):

I'm not sure if this is fixed in 14.3, but it just happened again. Clear cache fixed it.

@bbrendon commented on GitHub (Jul 29, 2022): I'm not sure if this is fixed in 14.3, but it just happened again. Clear cache fixed it.

kerem commented

2026-03-14 05:02:00 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 15, 2022):

I just made some changes today, so check this out on the next release.

@sadnub commented on GitHub (Aug 15, 2022): I just made some changes today, so check this out on the next release.