mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1742] Automation Manager - Policy - if you enable it after disable it first, the policy does not kick in, have to apply the policy on agents again #1084
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#1084
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 @wangshiok on GitHub (Jan 25, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1742
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
got a Automation Manager - Policy to restart server every Monday, and applied the policy to a group of agents. During Christmas/New year, I decided to suspend the policy, so instead of removing the policy from agent, I just disabled the policy from Automation Manager, after the new year break, I enabled the policy in Automation manager, and the policy is not working, you have to remove the policy and apply the policy again on agents.
To Reproduce
Steps to reproduce the behavior:
as ABOVE in Describe the bug
Expected behavior
as ABOVE in Describe the bug
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
@wh1te909 commented on GitHub (Jan 30, 2024):
I am not able to reproduce, seems to be working for me. I've recorded a video, please let me know if you are doing something different and provide exact steps to reproduce or a record a video if you can, thanks.
https://github.com/amidaware/tacticalrmm/assets/7434746/57fe54c1-fc25-4829-8ab0-321e29b0cad8
@wangshiok commented on GitHub (Jan 31, 2024):
thanks, see below screenshots, the task is there but not executing after I
re-enabled the policy after the Christmas/New year break, you can see the
task last run time was 18 -Dec-2023 before Christmas.
On Tue, 30 Jan 2024 at 20:01, Dan @.***> wrote:
@wangshiok commented on GitHub (May 15, 2024):
happy to close
@wangshiok commented on GitHub (May 15, 2024):
a quick work-around is to make a small change on the policy in automation manager, then you will notice on the related agents > "Will sync on next agent checkin", then it is all good.