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).
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).
/plugin marketplace add growthxai/output-claude-plugins/plugin install growthxai-outputai-plugins-outputai@growthxai/output-claude-pluginsThis skill is limited to using the following tools:
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.
npx output workflow result after confirming COMPLETED statusnpx output workflow debug for FAILED workflowsnpx output workflow runs list for multiple runsnpx output workflow status <workflowId>
Replace <workflowId> with the ID from npx output workflow start or npx output workflow runs list.
| 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 |
Scenario: Monitor a running workflow
# 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
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
# 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
# Check multiple workflows
for id in abc123 def456 ghi789; do
echo "Workflow $id: $(npx output workflow status $id)"
done
Workflows typically follow these paths:
RUNNING -> COMPLETED (success)
RUNNING -> FAILED (error occurred)
RUNNING -> TERMINATED (manually stopped)
RUNNING -> TIMED_OUT (exceeded limit)
The status command returns information including:
npx output workflow runs list to find the correct IDnpx output workflow debug <id>npx output workflow stop <id>npx output workflow debug for contextnpx output workflow startnpx 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 workflownpx output workflow runs list - View execution historyThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.