Skip to main content

Overview

Flows are automated workflows that define sequences of operations for data processing, transformation, or other administrative tasks. They can be run manually, scheduled, or triggered by events. Navigate to Admin > Data Sources > Flows.

Viewing Flows

The flows page displays a grid of flow cards, each showing:
  • Flow name and description
  • Status badge — Active, Running, Paused, or Draft
  • Schedule indicator (if the flow runs on a schedule)
  • Last execution time

Creating a Flow

  1. Click Create New Flow
  2. Define the flow name and description
  3. Use the visual flow editor to build your workflow
  4. Save and optionally activate the flow

Flow Editor

The flow editor provides a visual interface for building workflows by connecting steps and defining logic.

Flow Node Types

See Enrichment Rules for how to create and configure rules. The editor warns if the selected enrichment rule is invalid against the current ontology.

Running Flows

Manual Execution

Click Run Now on any flow card to execute it immediately. The status changes to Running and you can monitor progress in the execution details.

Scheduled Execution

Open a flow and click Schedule. Choose Daily or Weekly, a timezone, and a start time. A weekly schedule also needs at least one day. Save Schedule stores the next run. The flow’s Active switch must be on. A run that is already in progress is left alone until it finishes. The next run is the following day, or the following selected weekday.

Business-Hours Hold

A flow that re-scans and re-ingests your data writes to the knowledge graph, and the graph answers other questions more slowly while it does. To keep scheduled flows out of your working day, an administrator can set a business-hours window in System Settings (JOBS tab) with INGESTION_PEAK_HOURS, INGESTION_PEAK_TIMEZONE and INGESTION_PEAK_DAYS. The hold is off until INGESTION_PEAK_HOURS is set. While the window is open:
  • A scheduled flow that falls due does not start. It starts once, on the first runner pass after the window closes, and its next run is then set as usual.
  • Run Now, and a run that is already in progress, are never held.
The window is one setting for the whole deployment, written in its own time zone. It does not change a flow’s schedule: the time and time zone you choose in Schedule stay as they are, and a flow scheduled for the night simply never meets the window.

Monitoring Executions

Execution History

Each flow maintains a history of executions. View the list at the flow’s executions page, which shows:
  • Execution start and end times
  • Duration
  • Status (success, failure, in progress)
  • Number of items processed

Execution Details

Click any execution to see detailed information:
  • Step-by-step execution log
  • Input and output data for each step
  • Error messages for failed steps
  • Processing metrics

Managing Flows

Deleting a flow also removes its execution history. Export any important execution data before deleting.