Automate Platform Maintenance with System Flows
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append .md to any kestra.io/docs/* URL for plain Markdown.

System Flows are flows in the system namespace that automate recurring platform maintenance — running on a fixed cadence and kept separate from your user-facing executions.

Common uses include:

  1. Sending alert notifications
  2. Creating automated support tickets when critical workflows fail
  3. Purging logs and removing old executions or internal storage files to save space
  4. Syncing code from Git or pushing code to Git
  5. Automatically releasing flows from development to QA and staging environments

By default, System Flows are only visible within the system namespace and to users with appropriate access. To use a different namespace name, set the following in your Plugins and Execution configuration:

kestra:
  systemFlows:
    namespace: system

System Flows live in the system namespace, pinned at the top of Namespaces.

Namespaces list with system namespace pinned at the top

The Blueprints tab inside the system namespace provides ready-to-use templates you can customize for your organization.

System Blueprints tab showing maintenance flow templates including purge, Git sync, and failure alert blueprints

System flow executions appear across the Dashboard, Flows, and Executions pages. Use the Scope filter to view user and system executions separately or together.

Dashboard Scope filter with User executions and System executions options

The system namespace is open by default. Using namespace-level RBAC in the Enterprise Edition, you can restrict it to admins while assigning company.* namespaces to your general user base.

Was this page helpful?