/output-workflow-status
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).
$ npx -y skills add growthxai/output --skill output-workflow-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/output-workflow-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
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).
SKILL.md
output-workflow-status.SKILL.mdname: output-workflow-status
description: 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).
allowed-tools: [Bash]
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
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
# Start a workflow
npx output workflow start data-sync --input '{"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
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 --json
break
fi
sleep 10
done**Scenario**: Check before getting result
# 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 --json
**Scenario**: Batch status check
# 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
Read more
name: output-workflow-status description: 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). allowed-tools: [Bash]
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
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
# Start a workflow
npx output workflow start data-sync --input '{"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
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 --json
break
fi
sleep 10
done**Scenario**: Check before getting result
# 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 --json
**Scenario**: Batch status check
# 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
The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code — describe what you want, Claude builds it, with all the best practices already in place. One framework.
Repo: growthxai/output
Other skills on output.
- /llm-output-schema-constraints
Zod schema constraints that Anthropic rejects or silently ignores when sent as structured-output tool definitions via Output.object(). Use when writing or reviewing Zod schemas passed to Output.object(), or debugging structured-output validation errors.
Open skill - /prompt-file-provider-options
Guide to the providerOptions structure in .prompt files — decision tree for where an option goes, common mistakes, per-provider quick reference, and Anthropic prompt caching. Use when writing or reviewing .prompt file frontmatter (provider, model, providerOptions,
Open skill - /validate
Run lint, build, and tests to validate changes are correct
Open skill - /output-build-workflow
Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build.
Open skill - /output-credentials-edit
View and edit encrypted credentials in an Output.ai project. Use when adding secrets, updating API keys, verifying credential values, or retrieving a specific credential.
Open skill - /output-credentials-env-vars
Wire encrypted credentials to environment variables using the credential: convention. Use when setting up LLM provider keys (ANTHROPIC_API_KEY, OPENAI_API_KEY) or any env var that should come from encrypted credentials.
Open skill

