Skip to content

Tasks Triggered on Check Failure With Multi-Option/Multi-Condition #2380

@isv-one

Description

@isv-one

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions