output-workflow-status

Included with Lifetime

$97 forever

Check the status of an Output SDK workflow execution. Use when monitoring a running workflow, checking if a workflow completed, or determining workflow state (RUNNING, COMPLETED, FAILED, TERMINATED).

Backend & APIs

What this skill does


# Check Workflow Execution Status

## Overview

This skill checks the current execution status of a workflow. Use it to monitor running workflows, verify completion, or determine if a workflow failed before attempting to get its result.

## When to Use This Skill

- Monitoring a workflow started asynchronously
- Checking if a workflow has completed
- Determining why you can't get a workflow result
- Verifying workflow state before taking action
- Polling for completion in scripts

## When to Use Other Commands

- **Getting results**: Use `npx output workflow result` after confirming COMPLETED status
- **Debugging failures**: Use `npx output workflow debug` for FAILED workflows
- **Execution history**: Use `npx output workflow runs list` for multiple runs

## Instructions

### Check Status

```bash
npx output workflow status <workflowId>
```

Replace `<workflowId>` with the ID from `npx output workflow start` or `npx output workflow runs list`.

## Understanding Status Values

| Status | Meaning | Next Action |
|--------|---------|-------------|
| RUNNING | Workflow is currently executing | Wait and check again |
| COMPLETED | Workflow finished successfully | Get result with `npx output workflow result` |
| FAILED | Workflow encountered an error | Debug with `npx output workflow debug` |
| TERMINATED | Workflow was manually stopped | Review if expected, restart if needed |
| TIMED_OUT | Workflow exceeded time limit | Check for long operations, adjust timeout |

## Examples

**Scenario**: Monitor a running workflow

```bash
# Start a workflow
npx output workflow start data-sync '{"source": "external"}'
# Output: Workflow ID: sync-abc123

# Check status
npx output workflow status sync-abc123
# Output: Status: RUNNING

# Wait and check again
sleep 30
npx output workflow status sync-abc123
# Output: Status: COMPLETED
```

**Scenario**: Poll for completion in a script

```bash
WORKFLOW_ID="abc123xyz"

while true; do
  STATUS=$(npx output workflow status $WORKFLOW_ID)
  echo "Current status: $STATUS"

  if [[ "$STATUS" == *"COMPLETED"* ]]; then
    echo "Workflow completed!"
    npx output workflow result $WORKFLOW_ID
    break
  elif [[ "$STATUS" == *"FAILED"* ]]; then
    echo "Workflow failed!"
    npx output workflow debug $WORKFLOW_ID --format json
    break
  fi

  sleep 10
done
```

**Scenario**: Check before getting result

```bash
# Verify status first
npx output workflow status my-workflow-123

# If COMPLETED, get result
npx output workflow result my-workflow-123

# If FAILED, debug instead
npx output workflow debug my-workflow-123 --format json
```

**Scenario**: Batch status check

```bash
# Check multiple workflows
for id in abc123 def456 ghi789; do
  echo "Workflow $id: $(npx output workflow status $id)"
done
```

## Status Transitions

Workflows typically follow these paths:

```
RUNNING -> COMPLETED (success)
RUNNING -> FAILED (error occurred)
RUNNING -> TERMINATED (manually stopped)
RUNNING -> TIMED_OUT (exceeded limit)
```

## Interpreting Status Output

The status command returns information including:
- **Status**: Current state (RUNNING, COMPLETED, FAILED, etc.)
- **Duration**: How long the workflow has been running or ran
- **Start Time**: When the workflow began

## Troubleshooting

### "Workflow not found"
- The workflow ID may be incorrect
- The workflow may have been deleted from history
- Check `npx output workflow runs list` to find the correct ID

### Status stays RUNNING too long
1. Check if the workflow is stuck: `npx output workflow debug <id>`
2. Look for infinite loops or waiting operations
3. Consider stopping: `npx output workflow stop <id>`

### Unexpected TERMINATED status
- Someone may have manually stopped the workflow
- Check with `npx output workflow debug` for context
- Restart if needed: `npx output workflow start`

## Related Commands

- `npx output workflow result <id>` - Get execution result (after COMPLETED)
- `npx output workflow debug <id>` - Debug execution (after FAILED)
- `npx output workflow stop <id>` - Stop a running workflow
- `npx output workflow runs list` - View execution history

Files: 1

Size: 4.3 KB

Complexity: 13/100

Category: Backend & APIs

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

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