mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #604] After creating a task in Automation Manager, it is not assigned to agents. #2326
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#2326
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 @cm-slu on GitHub (Jun 29, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/604
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
When creating a task in automation manager which is executed following a script error, it is not assigned to the agents.
Whereas if I create the same task with a manual trigger, it is indeed assigned to the agents.
To Reproduce
For reproduce look this video
https://drive.google.com/file/d/1KIgDwCZ24Ah0I3_YBRh-UgW3UzNY46J_/view?usp=sharing
below is the download link of the script I want to run
https://drive.google.com/file/d/1Y2vHLkT5j4nIICw_4lo3gQgZGFCa9Szm/view?usp=sharing
Additional context
I want to run a task when the "Disk space check" is in error
@wh1te909 commented on GitHub (Jun 29, 2021):
thanks we need to see more settings though
where is the policy applied? client, site, or thru agent? any exclusions?
please show process of creating a new policy from the beginning
so start by creating a brand new policy
@cm-slu commented on GitHub (Jun 29, 2021):
where is the policy applied?
Client (no exclusion)
my policy is recent. It was created a few days ago
I just created a new test font and it works.
Do I still have to delete my policy?
It's a lot of work.
@wh1te909 commented on GitHub (Jun 29, 2021):
no need to delete. ok thanks let me try to reproduce
@cm-slu commented on GitHub (Jun 29, 2021):
ok good news lol.
if you need more trace of debug or other tell me no problem.
I think the reproduction on your side will be complicated as when I create a new policy it works. It has to be in my context.
@silversword411 commented on GitHub (Sep 21, 2021):
I think there was a fix about policies not applying. If still a problem please provide further info and we'll reopen.