[GH-ISSUE #1995] Multiple script checks based on the same script in an automation policy do not work. #3190

New issue

Closed

opened 2026-03-14 06:49:30 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 06:49:30 +03:00

Owner

Originally created by @janstalhut on GitHub (Sep 6, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1995

Server Info (please complete the following information):

OS: Debian 12
Browser: Firefox
RMM Version (as shown in top left of web UI): 0.19.3

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): 2.8.0
Agent OS: Linux (Maybe others too, I haven't tried that.)

Describe the bug
If I add a script check multiple times with different parameters via an automation policy, then this check only appears once for the agents to which this policy was assigned. Based on the email notifications I receive from this script, it seems to be random which of the script checks is actually executed on the agent.

To Reproduce
Steps to reproduce the behavior:

Create an Automation Policy with 2 script checks
Use the same script twice with different parameters
Asign the Policy
Have a look at checks view of the agent.

Expected behavior
If I enter multiple script checks via a policy, I expect that they will all be executed on the assigned agents.

Workaround:
Distribute the script to the agents only once using the policy and then assign further script checks with the same script individually at agent level. But of course this is very tedious and not really in the spirit of the policies.

Originally created by @janstalhut on GitHub (Sep 6, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1995 **Server Info (please complete the following information):** - OS: Debian 12 - Browser: Firefox - RMM Version (as shown in top left of web UI): 0.19.3 **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): 2.8.0 - Agent OS: Linux (Maybe others too, I haven't tried that.) **Describe the bug** If I add a script check multiple times with different parameters via an automation policy, then this check only appears once for the agents to which this policy was assigned. Based on the email notifications I receive from this script, it seems to be random which of the script checks is actually executed on the agent. **To Reproduce** Steps to reproduce the behavior: 1. Create an Automation Policy with 2 script checks 2. Use the same script twice with different parameters 3. Asign the Policy 4. Have a look at checks view of the agent. **Expected behavior** If I enter multiple script checks via a policy, I expect that they will all be executed on the assigned agents. **Workaround:** Distribute the script to the agents only once using the policy and then assign further script checks with the same script individually at agent level. But of course this is very tedious and not really in the spirit of the policies.

kerem closed this issue

2026-03-14 06:49:35 +03:00

kerem commented

2026-03-14 06:49:41 +03:00

Author

Owner

@silversword411 commented on GitHub (Sep 9, 2024):

Dupe https://github.com/amidaware/tacticalrmm/issues/1462

@silversword411 commented on GitHub (Sep 9, 2024): Dupe https://github.com/amidaware/tacticalrmm/issues/1462

kerem commented

2026-03-14 06:49:46 +03:00

Author

Owner

@janstalhut commented on GitHub (Sep 9, 2024):

I think there is some different between this issue an the #1462:
In #1462 will be multiple checks on the agent level while there are already the same check in a policy.
But I try to create simply multiple checks in one policy. There are no warning or error while do so, it finally doesn't work!

At the very least there should be a message if you tried to add the same script check to a policy one more time that this was not possible.

@janstalhut commented on GitHub (Sep 9, 2024): I think there is some different between this issue an the #1462: In #1462 will be multiple checks on the agent level while there are already the same check in a policy. But I try to create simply multiple checks in one policy. There are no warning or error while do so, it finally doesn't work! At the very least there should be a message if you tried to add the same script check to a policy one more time that this was not possible.