[GH-ISSUE #2380] Tasks Triggered on Check Failure With Multi-Option/Multi-Condition #3406

Open
opened 2026-03-14 07:16:59 +03:00 by kerem · 1 comment
Owner

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.

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.
Author
Owner

@P6g9YHK6 commented on GitHub (Dec 21, 2025):

https://github.com/amidaware/tacticalrmm/issues/2105

<!-- gh-comment-id:3678606829 --> @P6g9YHK6 commented on GitHub (Dec 21, 2025): https://github.com/amidaware/tacticalrmm/issues/2105
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#3406
No description provided.