Flows

Flows are AI-assisted runbooks designed for incident diagnosis and resolution. They combine structured procedures with intelligent automation to guide you through systematic troubleshooting.

What Makes Flows Different

Unlike simple checklists, flows include:

• Root Cause Modeling — Define the potential causes of problems
• Triage Steps — Investigation steps that diagnose and narrow down the root cause
• Remediation Steps — Actions to resolve each identified root cause
• Intelligent Routing — Outcomes from triage automatically route to appropriate remediation

Flows can execute fully automated, fully manual, or as a hybrid with AI handling routine steps while humans handle decisions.

Browsing Flows

Navigate to Flows in the sidebar to see available flows.

Quick Filters

Filter flows by performance and usage:

Filter	Description
High Performers	Flows with high success rates and consistency
Reliable	Flows with high Consistency Index
Fast	Flows with low average MTTR
Popular	Most frequently used flows
Needs Improvement	Flows with lower success rates
Recent	Recently created or modified
Active / Stale / Unused	Filter by usage patterns

Understanding Metrics

Each flow displays performance metrics:

• Success Rate — Percentage of runs completing successfully
• Consistency Index — How reliably the flow produces expected outcomes
• MTTR — Average time from run start to resolution
• Run Count — Total executions

Use these metrics to identify which flows are most effective and which need refinement.

Running a Flow

From the Flows Page

1. Click a flow to view its details
2. Review the description, symptoms, and structure
3. Click Run to start execution
4. Provide any required input variables
5. Follow the flow as it executes

From Chat

Ask the assistant to run a flow:

• "Run the database health check flow"
• "Start the network diagnostics flow for server web-prod-01"

The assistant finds matching flows and starts execution, prompting for inputs as needed.

During Execution

Automated Steps

When a step is automated, you'll see:

• The tool being executed
• Real-time progress
• Results and interpretation

The flow advances automatically based on outcomes.

Manual Steps

Some steps require human input:

• Answer diagnostic questions
• Confirm actions before execution
• Provide information the system can't gather automatically

The flow waits for your input before proceeding.

Viewing Progress

The run view shows:

• Current step and overall progress
• Step-by-step history
• Variable values
• Tool execution logs

Flow Lifecycle

States

State	Description
Draft	Work in progress, not available for general use
Active	Curated and approved for team use
Archived	Deprecated, kept for historical reference

Curation

Flows go through curation before becoming Active:

1. Draft — Initial creation, testing, refinement
2. Review — Team validates the flow works correctly
3. Active — Approved for production use

Only Active flows appear in the default browse view. You can filter to see Drafts you're working on.

Creating Flows

Via Chat (Recommended)

The easiest way to create a flow is through conversation:

1. Go to Chat
2. Describe your troubleshooting scenario:
   • "Create a flow for diagnosing database connection failures"
   • "Build a runbook for high memory usage on web servers"
3. The AI generates triage steps, root causes, and remediation based on:
   • Your description
   • Available tools
   • Knowledge base content
4. Review and refine through follow-up conversation
5. The flow is saved as a Draft for further editing

Manually

For full control, create flows manually:

1. Navigate to Flows
2. Click New
3. Define basics: title, description, symptoms
4. Add triage steps
5. Define outcomes and root causes
6. Add remediation steps
7. Configure variables
8. Test and publish

See Flow Editor for detailed editor instructions.

Ownership and Sharing

Every flow has an owner (the person who created it) and a sharing level that controls who can access it.

Sharing Levels

Level	Who Can View	Who Can Edit	Who Can Run
Personal	Only owner	Only owner	Only owner
Team	Your team members	Owner and team admins	Team members
Public	All users	Owner and admins	All users

Changing Sharing Settings

1. Open the flow's detail page
2. Click Settings or the sharing icon
3. Select the desired sharing level
4. Save

When to Use Each Level

Personal — Use for:

• Flows you're still developing
• Experimental or test flows
• Flows specific to your individual workflow

Team — Use for:

• Flows relevant to your team's responsibilities
• Standard operating procedures for your group
• Flows that need team review before wider release

Public — Use for:

• Organization-wide procedures
• Cross-team operational flows
• Flows that any user might need

Permissions by Role

Action	Owner	Team Admin	Team Member	Other Users
View (Team/Public)	Yes	Yes	Yes	Public only
Run	Yes	Yes	Yes	Public only
Edit	Yes	Yes (Team)	No	No
Delete	Yes	No	No	No
Change sharing	Yes	No	No	No

Start Personal, Then Share

Create flows as Personal while developing. Once tested and refined, change to Team or Public for broader access.

Best Practices

Start with Chat

Let the AI generate a first draft, then refine in the editor. This is faster than building from scratch.

Use Descriptive Titles

"Database Connection Issues" is better than "DB Flow". Good titles help others find your flows.

Define Clear Symptoms

Symptoms help match flows to incidents. Include error messages, metrics thresholds, or observable conditions.

Test Before Publishing

Use Test Run to validate your flow works correctly before making it Active.

Related Topics

• Flow Editor — Deep dive into building flows
• Runs — Track flow executions
• Chat — Create flows through conversation