output-workflow-runs-list

Included with Lifetime

$97 forever

List Output SDK workflow execution history. Use when finding failed runs, reviewing past executions, identifying workflow IDs for debugging, filtering runs by workflow type, or investigating recent workflow activity.

Backend & APIs

What this skill does


# List Workflow Execution History

## Overview

This skill helps you view the execution history of workflows. Use it to find failed runs, identify workflow IDs for debugging, and review past executions.

## When to Use This Skill

- Finding recent failed workflow runs
- Getting a workflow ID for debugging
- Reviewing execution history for a specific workflow
- Investigating when a problem started occurring
- Checking the status of recent executions

## Instructions

### List All Recent Runs

```bash
npx output workflow runs list
```

By default, this shows the 100 most recent workflow executions across all workflow types.

### Available Flags

| Flag | Description | Default |
|------|-------------|---------|
| `--limit <n>` | Number of runs to display | 100 |
| `--format <type>` | Output format: table, json, text | table |

### Filter by Workflow Name

```bash
npx output workflow runs list <workflowName>
```

This shows only runs for the specified workflow type.

### Get Detailed JSON Output

```bash
npx output workflow runs list --format json
```

Use JSON format for programmatic analysis or when you need full details.

## Understanding the Output

### Status Values

| Status | Meaning | Action |
|--------|---------|--------|
| RUNNING | Workflow is currently executing | Wait or monitor |
| COMPLETED | Workflow finished successfully | No action needed |
| FAILED | Workflow encountered an error | Debug with trace |
| TERMINATED | Workflow was manually stopped | Review if expected |
| TIMED_OUT | Workflow exceeded time limit | Check for long operations |

### Key Fields

When viewing runs, pay attention to:

- **Workflow ID**: Unique identifier needed for debugging commands
- **Status**: Current execution state
- **Start Time**: When the execution began
- **End Time**: When the execution completed (if finished)
- **Workflow Name**: The type of workflow that ran

## Examples

**Scenario**: Find failed workflow runs

```bash
# List recent runs and look for FAILED status
npx output workflow runs list --limit 20

# Or use JSON format with jq to filter
npx output workflow runs list --format json | jq '.[] | select(.status == "FAILED")'
```

**Scenario**: Get workflow ID for debugging

```bash
# List runs for a specific workflow
npx output workflow runs list my-workflow --limit 5

# Note the workflow ID from the output (e.g., "abc123xyz")
# Then debug it
npx output workflow debug abc123xyz --format json
```

**Scenario**: Review recent activity for a specific workflow

```bash
# See the last 10 runs of the data-pipeline workflow
npx output workflow runs list data-pipeline --limit 10
```

**Scenario**: Export run history for analysis

```bash
# Get all recent runs as JSON for external analysis
npx output workflow runs list --format json > workflow-runs.json
```

**Scenario**: Find when failures started

```bash
# Look at more history to find patterns
npx output workflow runs list --limit 50 --format json | jq 'group_by(.status) | map({status: .[0].status, count: length})'
```

## Identifying Problems

### Signs of Issues

1. **Multiple FAILED runs**: Indicates a persistent bug
2. **Mix of COMPLETED and FAILED**: Could be input-dependent issues
3. **All recent runs TERMINATED**: Someone may be stopping workflows
4. **Long RUNNING times**: Possible hang or performance issue

### Next Steps After Finding a Failed Run

1. Copy the workflow ID from the run
2. Get the execution trace: `npx output workflow debug <workflowId> --format json`
3. Analyze the trace to identify the failure
4. Apply the appropriate fix based on the error pattern

## Related Commands

- `npx output workflow debug <id>` - Analyze execution trace
- `npx output workflow status <id>` - Check current status
- `npx output workflow result <id>` - Get execution result
- `npx output workflow list` - List available workflows

Files: 1

Size: 4.0 KB

Complexity: 13/100

Category: Backend & APIs

Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-workflow-runs-list

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts