> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.komo.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Runs

> Monitor, debug, and manage workflow executions with detailed logs, filtering, and replay capabilities

# Workflow Runs

Workflow Runs provides comprehensive monitoring and debugging capabilities for all your workflow executions. View detailed logs, track performance, filter by criteria, and replay failed executions.

## Overview

The Workflow Runs section allows you to:

* **Monitor executions** - See all workflow runs in real-time
* **Debug issues** - View detailed step-by-step logs
* **Filter and search** - Find specific executions quickly
* **Replay runs** - Re-execute failed workflows
* **Track performance** - Analyze execution times and success rates

## Accessing Workflow Runs

### Navigation

1. Navigate to **Automations > Workflow Runs** in the sidebar
2. Or access from a specific site via **Site > Workflows > Workflow Runs**

### View Options

**Global View:**

* Shows all workflow runs across workspace
* Filter by site, workflow type, status
* Access from main navigation

**Site-Specific View:**

* Shows only workflows for specific site
* Filter by card, workflow type
* Access from site editor

## Workflow Run List

### Run Information Displayed

Each workflow run shows:

* **Workflow Name** - Which workflow executed
* **Version** - The workflow version the run executed against
* **Status** - Success, Failed, Running, or Pending
* **Start Time** - When execution began
* **Duration** - How long execution took
* **Site/Card** - Where workflow was triggered
* **Trigger** - What initiated the workflow

### Status Types

**Success ✅**

* All steps completed successfully
* No errors encountered
* Final action executed

**Failed ❌**

* One or more steps failed
* Error details available
* May require replay or manual intervention

**Running 🔄**

* Currently executing
* Steps in progress
* Real-time status updates

**Pending ⏳**

* Queued for execution
* Waiting for resources
* Will start automatically

## Filtering & Search

### Available Filters

**Date Range:**

* Today
* Last 7 days
* Last 30 days
* Custom range

**Status:**

* Success
* Failed
* Running
* Pending
* Multiple selection allowed

**Workflow Type:**

* Card workflows
* Site workflows
* Contact workflows
* Survey workflows
* Integration workflows

**Site/Card:**

* Filter by specific site
* Filter by specific card
* All sites option

**Trigger Type:**

* Manual trigger
* Automatic trigger
* API trigger
* Scheduled trigger

**Version:**

* Filter runs by the workflow version they executed against
* Select one or more versions to narrow results
* Available when viewing runs for a specific workflow

### Using Filters

1. Click **Filter** button
2. Select filter criteria
3. Apply filters
4. View filtered results
5. Clear filters to reset

### Filter Chips

Active filters display as chips:

* Click **X** to remove individual filters
* Click **Clear All** to remove all filters
* Filters persist in URL for sharing

## Viewing Run Details

### Execution Log

Click any workflow run to view detailed execution log. Run details are loaded fresh each time you open them to ensure you see the latest data.

**Overview Section:**

* Workflow name and ID
* Version name and number for each attempt
* Contact information
* Start and end times
* Total duration
* Final status
* Trigger information

**Step-by-Step Log:** Each workflow step shows:

* **Step Name** - Action performed
* **Status** - Success or failed
* **Timestamp** - When step executed
* **Duration** - How long step took
* **Input Data** - Data received by step
* **Output Data** - Data produced by step
* **Error Details** - If step failed

### Step Types Displayed

**Triggers:**

* Trigger type and conditions
* Contact or event that triggered workflow
* Timestamp of trigger

**Actions:**

* Action performed (email, tag, etc.)
* Target contact or entity
* Success/failure status
* Result details

**Conditions:**

* Condition evaluated
* Result (true/false)
* Branch taken

**Delays:**

* Delay duration
* Scheduled resume time
* Actual resume time

## Debugging Failed Runs

### Identifying Issues

**Failed Status:**

1. Locate failed run in list
2. Click to open details
3. Review step-by-step log
4. Identify failed step
5. View error message

### Common Failure Reasons

**Configuration Errors:**

* Missing required fields
* Invalid email addresses
* Incorrect API credentials
* Deleted resources referenced

**Data Issues:**

* Missing contact properties
* Invalid data formats
* Null values where required
* Data type mismatches

**External Service Failures:**

* Email service unavailable
* API timeouts
* CRM sync failures
* Webhook errors

**Logic Errors:**

* Infinite loops
* Missing condition branches
* Invalid variable references
* Timing issues

### Error Details

Each failed step shows:

* **Error Code** - Machine-readable error identifier
* **Error Message** - Human-readable description
* **Stack Trace** - Technical details (for advanced debugging)
* **Input Data** - Data that caused failure
* **Suggested Fix** - Recommended resolution

## Replaying Workflow Runs

### When to Replay

**Appropriate Scenarios:**

* Temporary external service failure
* Configuration since corrected
* Data issue now resolved
* Testing workflow changes

**Not Appropriate:**

* Contact no longer exists
* Workflow logic fundamentally changed
* Duplicate action concerns
* Compliance restrictions

### How to Replay

1. Open failed workflow run details
2. Click **Replay** button
3. Confirm replay action
4. System re-executes workflow
5. New run appears in list
6. Compare original vs. replay results

### Replay Options

**Exact Replay:**

* Uses original trigger data
* Same contact, same timing
* Identical starting conditions

**Modified Replay:**

* Adjust trigger data
* Change contact
* Modify timing
* Test variations

## Performance Analysis

### Execution Metrics

**Time Analysis:**

* Average execution time
* Slowest steps
* Bottleneck identification
* Duration trends over time

**Success Rates:**

* Overall success percentage
* Success by workflow type
* Success by time period
* Failure pattern analysis

**Volume Metrics:**

* Runs per day/week/month
* Peak execution times
* Queue depth
* Processing capacity

### Optimization Insights

**Slow Workflows:**

* Identify long-running workflows
* Review delay steps
* Check external API calls
* Optimize complex conditions

**High Failure Rates:**

* Workflows needing attention
* Common failure points
* Configuration improvements
* Error handling enhancements

## Best Practices

### Monitoring

**Regular Review:**

* Check failed runs daily
* Review long-running workflows
* Monitor success rate trends
* Set up alerts for failures

**Proactive Debugging:**

* Test workflows before publishing
* Use preview mode
* Validate with sample data
* Monitor initial runs closely

### Troubleshooting

**Investigation Steps:**

1. Identify failure pattern
2. Review recent changes
3. Check external services
4. Validate data quality
5. Test in isolation
6. Implement fix
7. Monitor replay

**Documentation:**

* Note common issues
* Document solutions
* Share with team
* Update workflow comments

## FAQ

**Q: How long are workflow runs stored?** A: Workflow run history is retained based on your plan. Contact support for specific retention periods.

**Q: Can I export workflow run data?** A: Yes, use the export feature to download run data as CSV for analysis.

**Q: What's the difference between replay and clone?** A: **Replay** re-executes the same workflow with original data. **Clone** creates a copy of the workflow definition for editing. When you clone a workflow, a confirmation modal lets you enter a custom name for the new copy (max 50 characters). The cloned workflow is created in Draft status so you can modify it before activating.

**Q: Can I stop a running workflow?** A: Yes, click the running workflow and select **Stop Execution**. Note that already-completed steps cannot be undone.

**Q: Why do some workflows show as "Pending" for a long time?** A: Pending workflows are queued. High volume, complex workflows, or external API delays can increase queue time.

**Q: Can I see workflow runs from deleted cards or sites?** A: Yes, workflow runs are retained even if the triggering card or site is deleted, for historical analysis.

**Q: How do I set up alerts for workflow failures?** A: Use workflow triggers to send notifications on failure, or set up monitoring via the API.

**Q: Can multiple people view workflow runs simultaneously?** A: Yes, workflow runs are visible to all workspace members with appropriate permissions.

## Related Documentation

* [Workflows & Automation](/integrations-automation/workflows)
* [Workflow Triggers](/integrations-automation/workflows/triggers)
* [Workflow Actions](/integrations-automation/workflows/actions)
* [Debugging Workflows](/integrations-automation/workflows/workflow-runs)
* [API Documentation](https://api.komo.site/api/v1/public/api-docs)

***

**Need Help?** Contact [support@komo.tech](mailto:support@komo.tech) for workflow debugging assistance.