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 simplify proactive diagnostic actions, quickly solve issues when there's a focus on their detection, and provide a very efficient way to enable self-remediation mechanisms over common problems. It also allows technical teams to couple devices to configurations defined by the organization, evaluating them periodically and adapting them if necessary.

The overview shows the list of flows created in the organization. The information gathered in the table is as follows:

• Name. Name of the flow.

• Description. Purpose of the flow.

• Type. The 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.

• Detection only. Evaluates conditions as a "sampling" method. Detects those devices where the conditions are met but does not execute the microservice defined in the flow.

• 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.

• Action. Contains the See details button, which allows customizing the flow's behavior through the following options: Overview, Destination, Flow, and Notification.

In the top right corner of the flow detail view, there is a button that allows you to enable or disable it.

Overview

Stores general information of the flow.

• Description. Purpose of the flow.

• Type. The 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. Evaluates conditions as a "sampling" method. Detects those devices where the conditions are met but does not execute the microservice defined in the flow.

• Status. Indicates if the flow is enabled or disabled.

• Created on. Date the flow was created.

• Update date. Date the flow was updated.

Edit and delete a flow

Using the Edit button, you can change the name, description, and reuse time of the flow.

• The Detection Only checkbox allows you to activate or deactivate the Detection Only execution mode, in which the compliance with the conditions defined in the flow is evaluated, but the microservice is not executed.
• The Delete button allows you to delete a flow.

Target

This setting defines the device groups on which the flow will be executed. It supports the following configuration options:

• All devices
• A custom selection of devices
• One or more device groups
• One or several reporting groups

Flow

From here, you can define the conditions to evaluate, the required thresholds, and the action that will be executed if those conditions are met.

Flow conditions

These conditions allow triggering actions within the flow. All the conditions described below are compatible with the Windows operating system.

Existence of an ongoing process

Periodically checks if there is a process running, at configurable 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

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 defining a Recurrence Pattern with 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.

At the top of the form, a (text) summary of the configured schedule is displayed to confirm 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 standard UTC (Coordinated Universal Time).

info

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.

Actions

Once the conditions are evaluated and according to the obtained values, one or more actions can be executed. In this section, all the microservices enabled in your subscription will be displayed to select and include them in the flow.

Notification

This parameter is optional and can be disabled. It is used to send notifications to users at the start and end of the flow executions, using the operating system's notifications. Once enabled, you can set:

• Initial message. It will be sent to users at the start of the execution.
• Success message. It will be sent to users upon a successful execution.
• Error message. It will be sent to users upon an execution with errors.

info

A configuration change in an existing flow can take up to 15 minutes to apply to all linked devices.

tip

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