-
Notifications
You must be signed in to change notification settings - Fork 72
Description
Acknowledgements
- I have searched (https://github.com/utmstack/UTMStack/issues) for past instances of this issue
- I have verified that my UTMStack version is up-to-date
Describe the bug
In the SOAR Flows view, there are two functional inconsistencies affecting agent selection and trigger behavior
Incorrect Agent Selection Behavior
When the Agent Platform = Windows, the SOAR UI does not allow selecting a default agent.
Additionally, the label “Default Agent” is misleading. The correct terminology should be “Dedicated Agent”, since this agent is explicitly assigned to run the flow.
SOAR flows currently execute by default on the datasource associated with the alert that triggered the flow.
However, if the user configures a trigger without selecting an alert (e.g., using only additional filters), the system has no reliable way to determine which datasource should be used.
This creates ambiguity and may cause the flow to run against the wrong datasource or fail silently.
Regression Issue
- Select this option if this issue appears to be a regression.
Expected Behavior
The Flow Trigger configuration should always enforce:
- Selecting an Alert Name first
- Allowing the user to add any additional trigger conditions afterward
This ensures the system always knows which alert—and therefore which datasource—the flow should operate on.
Current Behavior
Windows agents cannot be selected as the default/dedicated agent
The UI label “Default Agent” is incorrect
Trigger configuration allows flows to be created without specifying an alert, causing datasource ambiguity
Reproduction Steps
- Open SOAR → Flows
- Create or edit a flow
- Set Agent Platform = Windows
- Attempt to select a default agent
- Configure a trigger without selecting an alert name
- Observe that the system cannot determine the datasource
Possible Solution
No response
Additional Information/Context
No response
UTMStack Version
11.2.2
Operating System and version
Ubuntu
Hypervisor and Version | Server Vendor and Model
Browser and version
Google Chrome
Metadata
Metadata
Assignees
Labels
Type
Projects
Status