mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1462] This check is overriden by a policy when a script is applied twice #915
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#915
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kiekeboe100 on GitHub (Mar 26, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1462
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
When applying a script check multiple times to an agent (but with different parameters), AND an automation policy is applied (with different checks, not necessarily the same ones), all but one of those "duplicate" script checks are shown as "This check is overriden by a policy" and aren't checked.
To Reproduce
Steps to reproduce the behavior:
Assign an automation policy to a company with "script check x"
Assign "script check y" with argument 1 to an agent in that company
Assign "script check y" with argument 2 to the same agent
Assign "script check y" with argument 3 to the ame agent
Expected behavior
All three "script check y" should run. As it does without an automation policy applied.
Screenshots
With automation policy applied
Without automation policy applied
Additional context
Not necessary I think.
@silversword411 commented on GitHub (Mar 26, 2023):
So this is probably the same issue that comminuty scripts used to have pre GUIDs, they were just checked for by name?
@P6g9YHK6 commented on GitHub (May 15, 2024):
same issue on my side
FYI the same check is also set in the policy and disappear on the device. this is expected and good.
when the policy is blocked the checks can be duplicated
@Kieran-staffs-tech commented on GitHub (Jun 5, 2025):
Same issue, shame this hasn't seen any traction.