[GH-ISSUE #2273] Tasks in automation policies do not update based on the default arguments provided in the script source #3356

New issue

Open

opened 2026-03-14 07:12:06 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 07:12:06 +03:00

Owner

Originally created by @isv-one on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2273

Server Info (please complete the following information):

OS: Hosted by Amidaware
Browser: Safari, Chromium
RMM Version (as shown in top left of web UI): 1.2.0

Installation Method:

[ x ] Standard
Standard with --insecure flag at install
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): Server issue
Agent OS: [e.g. Win 10 v2004, Server 2016] Server issue

Describe the bug
A clear and concise description of what the bug is.
Scripts with arguments applied as Tasks to automation policies do not update their arguments upon updating the source script file with its default/saved arguments. Defaults from source are important. If exceptions are made, they are made in a new file/instance of the script.

To Reproduce
Steps to reproduce the behavior:

Create a script that includes several arguments/parameters
Apply that script as a Task to an Automation Policy
The flow takes you through the script/command selection, which includes all of the arguments at the present version of the script with its default arguments. These are individual items and seemingly cemented into the Task even upon updating the arguments in the default/source script later

Expected behavior
Tasks will inherit the DEFAULT arguments in the source script when they change in the source script. Arguments specified outside of default should obviously be retained for individual use-cases.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Originally created by @isv-one on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2273 **Server Info (please complete the following information):** - OS: Hosted by Amidaware - Browser: Safari, Chromium - RMM Version (as shown in top left of web UI): 1.2.0 **Installation Method:** - [ x ] Standard - [ ] Standard with `--insecure` flag at install - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): Server issue - Agent OS: [e.g. Win 10 v2004, Server 2016] Server issue **Describe the bug** A clear and concise description of what the bug is. Scripts with arguments applied as Tasks to automation policies do not update their arguments upon updating the source script file with its default/saved arguments. Defaults from source are important. If exceptions are made, they are made in a new file/instance of the script. **To Reproduce** Steps to reproduce the behavior: 1. Create a script that includes several arguments/parameters 2. Apply that script as a Task to an Automation Policy 3. The flow takes you through the script/command selection, which includes all of the arguments at the present version of the script with its default arguments. These are individual items and seemingly cemented into the Task even upon updating the arguments in the default/source script later **Expected behavior** Tasks will inherit the DEFAULT arguments in the source script when they change in the source script. Arguments specified outside of default should obviously be retained for individual use-cases. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.

kerem commented

2026-03-14 07:12:12 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (Aug 13, 2025):

this could have unintended consequences if implemented

i for example count on this behavior to customize per policy the arguments

@P6g9YHK6 commented on GitHub (Aug 13, 2025): this could have unintended consequences if implemented i for example count on this behavior to customize per policy the arguments