[GH-ISSUE #80] Policies not applying tasks #42

New issue

Closed

opened 2026-03-02 02:13:04 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 02:13:04 +03:00

Owner

Originally created by @bradhawkins85 on GitHub (Aug 27, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/80

Originally assigned to: @sadnub on GitHub.

When applying a policy to a client or site checks are applied as expected however tasks do not apply.

Applying a policy directly to an agent pops up an error "Something went wrong" but nothing appears in the debug logs although the policy does apply, this also pulls down the site policy to the agent and creates the tasks.

Originally created by @bradhawkins85 on GitHub (Aug 27, 2020). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/80 Originally assigned to: @sadnub on GitHub. When applying a policy to a client or site checks are applied as expected however tasks do not apply. Applying a policy directly to an agent pops up an error "Something went wrong" but nothing appears in the debug logs although the policy does apply, this also pulls down the site policy to the agent and creates the tasks.

kerem closed this issue

2026-03-02 02:13:04 +03:00

kerem commented

2026-03-02 02:13:05 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 27, 2020):

I think I found the issue with this. Getting a fix together now. I wasn't able to replicate the policies being applied directly to the agent though. Does anything show up in the JS console when that happens?

@sadnub commented on GitHub (Aug 27, 2020): I think I found the issue with this. Getting a fix together now. I wasn't able to replicate the policies being applied directly to the agent though. Does anything show up in the JS console when that happens?

kerem commented

2026-03-02 02:13:05 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 27, 2020):

Just submitted the PR that will fix this. It appears the policy task creation would happen before the checks were created on the agent. Thanks for testing!

@sadnub commented on GitHub (Aug 27, 2020): Just submitted the PR that will fix this. It appears the policy task creation would happen before the checks were created on the agent. Thanks for testing!

kerem referenced this issue

2026-03-14 01:48:50 +03:00

[GH-ISSUE #42] Skip letsencrypt when sitting behind an existing reverse proxy #1956