mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #2380] Tasks Triggered on Check Failure With Multi-Option/Multi-Condition #3406
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#3406
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 @isv-one on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2380
Is your feature request related to a problem? Please describe.
Currently, Tasks that are configured to fire off when a Check fails can only be triggered by the script exiting code 1 (I think, but maybe also code 98)
Describe the solution you'd like
During the setup of a Task where the condition for trigger is a Check failure, add the option for multiple conditions to trigger, i.e.,
Check script/condition exit code 1 = Fire off Task script #1
Check script/condition exit code 12 = Fire off Task script #2
Check script/condition exit code 45 = Fire off Task script #3
Check script/condition exit code 9 = Fire off Task script #4
Afterward, an option/automation flow to trigger a re-Check of the failed Check, effectively "looping" back around.
Describe alternatives you've considered
The only way to achieve this behavior currently is to create specific Check/Tasks conditions that match up exactly with what you're looking to accomplish. While possible, this is tedious and noisy on the dashboard, and adds complexity to the workflow/automation policies.
Additional context
Add any other context or screenshots about the feature request here.
@P6g9YHK6 commented on GitHub (Dec 21, 2025):
https://github.com/amidaware/tacticalrmm/issues/2105