[GH-ISSUE #1852] Agent history shows the name of the alert action script instead of the alert resolved script #1158

New issue

Closed

opened 2026-03-02 02:21:33 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 02:21:33 +03:00

Owner

Originally created by @sebvonhelsinki on GitHub (Apr 22, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1852

Originally assigned to: @wh1te909 on GitHub.

Server Info (please complete the following information):

OS: Debian 12
Browser: Firefox
RMM Version (as shown in top left of web UI): 0.18.2

Installation Method:

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): v2.7.0
Agent OS: Windows Server 2012R2 (yes, it's EOL. No, I don't think that has anything to do with the issue at hand)

Describe the bug
I created two scripts: "Failure_Action_CreateTicket" and "Resolve_Action_CloseTicket". As the name implies, these are used in an alerting template to create or close tickets in our issue tracking system. However, the history shows the name of the "Failure_Action_CreateTicket" as the executed script no matter if an alert was triggered or resolved.

To Reproduce
Steps to reproduce the behavior:

Create two scripts
Create an Alert Template
In the Alert Template, under Alert Actions, set one script in "Alert Failure Settings" and the other under "Alert Resolved Settings"
Apply the template to an agent
Create a check that will always fail (i.e.: pingcheck to a private IP range different from the one the agent is part of)
Wait for the check to fail. The agent history should show an action "Script Run", the name of the script set at Alert Failure Settings, and Initiated by "alert-action-failure"
resolve the check (i.e.: change the IP in the ping-check to the IP of a known active device)
wait for the check to resolve. The agent history now shows an action "Script Run", still the name of the script set at Alert Failure Settings, but Initiated by "alert-action-resolved"

Expected behavior
The history should show that the script "Resolve_Action_CloseTicket" has been run.

Screenshots
Screenshot of the Alert template:

Screenshot of the client history:

Additional context
My understanding is that this is only a display error in the History section of the agents. The scripts I wrote and the alert template work as intended and tickets are created and closed as expected, so I can confirm that the alert template actually runs the second script as it should. The "output" column in the History section also returns the output I expect form the second script.

Originally created by @sebvonhelsinki on GitHub (Apr 22, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1852 Originally assigned to: @wh1te909 on GitHub. **Server Info (please complete the following information):** - OS: Debian 12 - Browser: Firefox - RMM Version (as shown in top left of web UI): 0.18.2 **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): v2.7.0 - Agent OS: Windows Server 2012R2 (yes, it's EOL. No, I don't think that has anything to do with the issue at hand) **Describe the bug** I created two scripts: "Failure_Action_CreateTicket" and "Resolve_Action_CloseTicket". As the name implies, these are used in an alerting template to create or close tickets in our issue tracking system. However, the history shows the name of the "Failure_Action_CreateTicket" as the executed script no matter if an alert was triggered or resolved. **To Reproduce** Steps to reproduce the behavior: 1. Create two scripts 2. Create an Alert Template 3. In the Alert Template, under Alert Actions, set one script in "Alert Failure Settings" and the other under "Alert Resolved Settings" 4. Apply the template to an agent 5. Create a check that will always fail (i.e.: pingcheck to a private IP range different from the one the agent is part of) 6. Wait for the check to fail. The agent history should show an action "Script Run", the name of the script set at Alert Failure Settings, and Initiated by "alert-action-failure" 7. resolve the check (i.e.: change the IP in the ping-check to the IP of a known active device) 8. wait for the check to resolve. The agent history now shows an action "Script Run", still the name of the script set at Alert Failure Settings, but Initiated by "alert-action-resolved" **Expected behavior** The history should show that the script "Resolve_Action_CloseTicket" has been run. **Screenshots** Screenshot of the Alert template: ![grafik](https://github.com/amidaware/tacticalrmm/assets/167771795/c5f5f375-90bf-4ed1-86e6-76857f5071fe) Screenshot of the client history: ![grafik](https://github.com/amidaware/tacticalrmm/assets/167771795/28772bd5-e4c4-4930-976e-95f52eff15cf) **Additional context** My understanding is that this is only a display error in the History section of the agents. The scripts I wrote and the alert template work as intended and tickets are created and closed as expected, so I can confirm that the alert template actually runs the second script as it should. The "output" column in the History section also returns the output I expect form the second script.

kerem

2026-03-02 02:21:33 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 02:21:34 +03:00

Author

Owner

@wh1te909 commented on GitHub (Apr 22, 2024):

thanks, fix will be in next release (for new entries only, can't fix what's already in db)

@wh1te909 commented on GitHub (Apr 22, 2024): thanks, fix will be in next release (for new entries only, can't fix what's already in db)

kerem commented

2026-03-02 02:21:34 +03:00

Author

Owner

@sebvonhelsinki commented on GitHub (Apr 23, 2024):

Great, thanks for the quick fix!

@sebvonhelsinki commented on GitHub (Apr 23, 2024): Great, thanks for the quick fix!

kerem referenced this issue

2026-03-14 04:58:43 +03:00

[GH-ISSUE #1158] Share your TRMM Benchmarks #2657