Skip to main content
Version: 25.6

Flows

Flows is a feature that allows you to define automation sequences to execute scheduled actions on devices based on the evaluation of predefined logical conditions.

This tool simplifies proactive diagnostic actions, quickly resolves issues when focused on detection and offers a very efficient way to enable mechanisms for self-remediation in recurring incidents. It also allows technical teams to align devices with the configurations defined by the organization, evaluating them periodically and adapting when required.

flows-v2

The list view presents the flows created in the organization, along with the following information:

  • Name. Name of the flow.

  • Description. Purpose of the flow.

  • Type. This is the execution scope of the flow, determined by the type of microservice you want to run. It can be configured at a user session level, with the corresponding permissions, or at a device level, with administrative access.

  • Detection only. If enabled, this means that the conditions will be evaluated in a "sampling" mode to detect those devices where they are met, but the defined microservice will not be executed.

  • Cooldown. Defines the minimum period that must pass before a condition is re-evaluated after it has been fulfilled and an action executed:

    • When a flow condition is met, an action is executed.
    • Begin counting the cooldown.
    • During this time, it will not be re-evaluated whether the condition is met.
    • Once the period has passed, the condition will be evaluated again.

    For example, if the cooldown is set for 24 hours, the condition will be evaluated and executed (if met) once a day, even if the condition remains active.

    The cooldown does not apply when the action is a microservice that restarts the device. In this case, if the condition is met, the action is executed without waiting.

    info

    If FlexxAgent or the device is restarted, the cooldown timer is interrupted and starts from zero.

  • Enabled. Indicates if the flow is Enabled or Disabled.

By clicking on a table record, you access the details of its configuration:

Above the table, the New button allows you to create a flow. For more information, please check this guide.

Overview​

Stores the flow configuration data. It is divided into three tabs:

overviewSection-v2

Overview​

Provides general information about the flow.

overview-flowsV2

  • Description. Purpose of the flow.

  • Type. Execution scope of the flow, determined by the type of microservice you want to run. It can be done at the user session level, with the corresponding permissions, or at the device level, with administrative access.

  • Version. Version number of the flow. Every time it is edited, the counter increments by 1.

  • Cooldown. Defines the minimum period that must pass before a condition is re-evaluated after it has been fulfilled and an action executed:

    • When a flow condition is met, an action is executed.
    • Begin counting the cooldown.
    • During this time, it will not be re-evaluated whether the condition is met.
    • Once the period has passed, the condition will be evaluated again.

    For example, if the cooldown is set for 24 hours, the condition will be evaluated and executed (if met) once a day, even if the condition remains active.

    The cooldown does not apply when the action is a microservice that restarts the device. In this case, if the condition is met, the action is executed without waiting.

    info

    If FlexxAgent or the device is restarted, the cooldown timer is interrupted and starts from zero.

  • Detection only. If enabled, this means that the conditions will be evaluated in a "sampling" mode to detect those devices where they are met, but the defined microservice will not be executed.

Notification​

Details the notifications that the operating system will send to users at the start and end of the flow executions.

notif-flowsV2

  • Initial text. Content of the notification that will be sent to users at the start of the execution.
  • Success text. Content of the notification that will be sent to users after a successful execution.
  • Error text. Content of the notification that will be sent to users after an execution with errors.

Target​

Specifies the devices or groups of devices where the flow will be executed.

  • All workspaces. All devices in the organization.
  • Workspaces. Specific devices.
  • Workspace groups. Specific workspace groups.
  • Report groups. Specific report groups.

Flow​

Shows the flow diagram: the conditions to evaluate, the required thresholds, and the action that will be executed on the device if the parameters are met.

For more information on how to create a flow, please check this guide.

flows-flowsV2

Flow conditions​

Flow conditions allow you to define the criteria under which the automated actions will trigger. All conditions described below are compatible with devices operating with the Windows operating system.

Existence of an ongoing process​

Performs periodic evaluations to verify if a process is running, with adjustable intervals between 15 seconds and 5 minutes.

Detected Windows event log record identifier​

Searches for specific events in the Windows Event Viewer, at intervals of 5 to 20 minutes.

Events are identified by the format:

<logName>:<Provider>:<id>

Example:

System:Microsoft-Windows-Winlogon:7001

Where:

  • logName = System
  • Provider = Microsoft-Windows-Winlogon
  • id = 7001

evwin

Operating system version​

Gets the operating system version at intervals between 1 and 12 hours, using operators that allow comparing if the value is equal, starts with, ends with, or contains a specific string.

Operating system language​

Detects the operating system language at intervals of 1 to 12 hours, using operators that allow comparing if the value is equal, starts with, ends with, or contains a specific string.

Operating system disk free space percentage​

Evaluates the free disk space, allowing setting a target percentage. It is checked at intervals of 5 to 60 minutes.

Cron Match​

Checks if the current date and time match the schedule defined graphically in the Value field. If there is a match, the scheduled action will be executed.

  • Check every. Specifies how often the system will evaluate if the schedule is met. This value must be adjusted according to the indicated schedule.
  • Value. Allows you to configure the schedule, periodicity, and recurrence that will determine when the action will be executed.

The form allows you to define a Recurrence Pattern through the following options:

  • Daily. Indicates what time and every how many days the action should be executed, as well as whether it should only be performed from Monday to Friday.
  • Weekly. Lets you define what time, every how many weeks, and on what days of the week the action will be executed.
  • Monthly. Sets what time and on what day of the month the action will be executed.
  • Interval. Determines how many minutes between each execution of the action within a day or a specific time range.
  • Custom Cron. Allows manual entry of a string in the standard cron format, useful for custom and advanced configurations.

cron-match

At the top of the form, a summary (in text) of the scheduled configuration is displayed to confirm that it is the desired one.

The hours are defined according to the time zone of the user editing the Cron Match, except in the case of a Custom Cron, where the hours are specified in the standard UTC time.

There are many references available to check the cron scheduling syntax. For example: crontab.guru

info

If you wish to implement custom flow conditions — such as evaluating uptime in days, checking the current status of services, or any other parameter that can be analyzed locally from the device — please consult with Flexxible.

Action's​

Actions are the microservices that have been programmed to automatically run when the predefined flow conditions are met.

To add an action when creating or modifying a flow, click on the corresponding condition and then select Add condition to choose one of the available microservices.

actions-flowsV2

The microservices will only appear in the list if they are enabled for the organization. For more information on how to enable them, please consult the Microservices documentation.

Flow Management​

Once a flow is created, it can be managed through the following options:

config-flowV2

Enable/Disable Flow​

Allows activating or deactivating the flow within an organization. The current state of the flow can be checked from the table containing the flow list or in Overview.

enabled-flowsV2 disabled-flowsV2

Edit - Overview, Notification, and Target​

Clicking on Edit from the Overview, Notification, or Target tabs allows you to modify settings defined during the creation of the flow.

  • Overview

    Allows editing the name of the flow, its description, execution scope, reuse time, and the option to execute or not the microservice once the conditions are met. Each field is explained in the Overview section and in the guide Schedule microservices execution.

    edit-overviewV2

  • Notification

    Allows enabling or disabling sending notifications to users and editing their content. The available message types are explained in the Notification section and in the guide Schedule microservices execution.

    edit-notifiV2

  • Target

    Allows defining the target devices for the flow. From the Apply to button, you can choose whether the flow will apply to all devices in the organization, specific devices, workspace groups, or report groups.

    edit-targetV2

Edit - Flow​

If you click on Edit from the Flow tab, you will be able to modify the conditions and actions that make it up.

edit-flowV2

info

Changes made in a flow can take up to 15 minutes to apply to all linked devices.

Delete​

Allows permanent removal of the flow.

remove-flowsV2