mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 23:15:57 +03:00
[GH-ISSUE #1733] Alert Template Not Updating with Automation Policy Change in Tactical RMM #1079
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#1079
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 @dinger1986 on GitHub (Jan 10, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1733
Description:
In Tactical RMM, changing the automation policy for an agent does not update the associated alert template as expected. This issue was discovered while troubleshooting delayed SMS alerts for offline servers. Despite changing an agent's type to 'server' and applying the 'server default' automation policy directly to the agent/PC, the alert template remains unchanged. This behavior persists even after performing a bulk update to the offline overdue time setting.
Steps to Reproduce:
Assign the 'server default' automation policy directly to an agent/PC.
Change the agent's type from 'workstation' to 'server'.
Observe that the alert template does not update in accordance with the automation policy change.
Expected Behavior:
Assigning a new automation policy or changing an agent's type should update the alert template to reflect the settings defined in the automation policy.
Actual Behavior:
The alert template remains unchanged despite changing the automation policy and agent type, leading to inconsistencies in alert management.
Additional Information:
The issue was initially identified during a power outage when servers went offline, but SMS alerts for data being overdue were not received as expected.
The default setting for data overdue was discovered to be set to half an hour, which was adjusted to 4 minutes for testing.
The primary issue regarding delayed SMS alerts was resolved; however, the problem with alert templates not updating persisted.
Reported on discord.
Environment:
Tactical RMM Version: 17.2
Operating System: Debian 11
@tkintenn commented on GitHub (Jan 10, 2024):
I have this problem as well. 17.3, debian 11.
@P6g9YHK6 commented on GitHub (Jan 13, 2024):
same here debian 12 / 17.3
this is quite a big deal of inconsistent behavior
screenshot of 2 devices moved from a client without AT to a client with AT
screenshot of the same client after removing the Automation policy and re-adding it to the client.
@wh1te909 commented on GitHub (Jan 30, 2024):
fixed, will be in next release