output-workflow-trace

Included with Lifetime

$97 forever

Analyze Output SDK workflow execution traces. Use when debugging a specific workflow, examining step failures, analyzing input/output data, understanding execution flow, or when you have a workflow ID to investigate.

Backend & APIs

What this skill does


# Workflow Trace Analysis

## Overview

This skill provides guidance on retrieving and analyzing workflow execution traces using the Output CLI. Traces show the complete execution history including step inputs, outputs, errors, and timing information.

## When to Use This Skill

- You have a workflow ID and need to understand what happened
- A workflow failed and you need to identify which step failed
- You need to examine the input/output data at each step
- You want to understand the execution flow and timing
- You need to find error messages and stack traces
- Debugging retry behavior or unexpected results

## Instructions

### Step 1: Retrieve the Execution Trace

**Basic trace (text format, may be truncated):**
```bash
npx output workflow debug <workflowId>
```

**Full trace (JSON format, recommended for detailed analysis):**
```bash
npx output workflow debug <workflowId> --format json
```

**Tip**: Always use `--format json` when you need complete trace data. The text format truncates long values which can hide important debugging information.

### Step 2: Analyze the Trace

Follow this checklist when examining a trace:

1. **Identify the failed step**: Look for steps with error status or failure indicators
2. **Examine error messages**: Find the exact error message and stack trace
3. **Check step inputs**: Verify the data passed to the failing step was correct
4. **Check step outputs**: Look at outputs from preceding steps
5. **Review retry attempts**: Note how many retries occurred and their outcomes
6. **Check timing**: Look for unusual delays that might indicate timeouts

### Step 3: Use the Temporal UI for Visual Analysis

Open **http://localhost:8080** in your browser for a visual workflow inspection:

1. Search for your workflow by ID
2. View the event history timeline
3. Click on individual events to see details
4. Inspect step inputs and outputs
5. See retry attempts and timing information
6. Export trace data if needed

## What to Look For in Traces

### Error Patterns

| Error Message | Likely Cause |
|---------------|--------------|
| "incompatible schema" | Zod import issue - using `zod` instead of `@outputai/core` |
| "non-deterministic" | Using Math.random(), Date.now(), etc. in workflow code |
| "FatalError" with retry context | Try-catch wrapping step calls |
| "undefined is not a function" | Missing schema definitions |
| "workflow must be deterministic" | Direct I/O in workflow function |
| "ECONNREFUSED" or timeout | Services not running or network issues |

### Step Status Values

- **COMPLETED**: Step finished successfully
- **FAILED**: Step threw an error (may retry)
- **RETRYING**: Step is being retried after a failure
- **TIMED_OUT**: Step exceeded its timeout
- **CANCELLED**: Workflow was stopped before step completed

### Key Trace Fields

When examining JSON traces, focus on these fields:

- `steps[].name`: Step identifier
- `steps[].status`: Execution result
- `steps[].input`: Data passed to the step
- `steps[].output`: Data returned from the step
- `steps[].error`: Error details if failed
- `steps[].attempts`: Number of execution attempts
- `steps[].duration`: How long the step took

## Examples

**Scenario**: Debug a failed workflow

```bash
# Get the workflow ID from runs list
npx output workflow runs list --limit 5 --format json

# Get detailed trace
npx output workflow debug abc123xyz --format json

# Look for the failing step in the output
# Example output structure:
# {
#   "workflowId": "abc123xyz",
#   "status": "FAILED",
#   "steps": [
#     { "name": "fetchData", "status": "COMPLETED", ... },
#     { "name": "processData", "status": "FAILED", "error": "..." }
#   ]
# }
```

**Scenario**: Investigate retry behavior

```bash
npx output workflow debug abc123xyz --format json | jq '.steps[] | select(.attempts > 1)'
```

**Scenario**: Check inputs to a specific step

```bash
npx output workflow debug abc123xyz --format json | jq '.steps[] | select(.name == "processData") | .input'
```

## Next Steps After Analysis

1. Match the error to common patterns (see error skills)
2. Consult the `workflow-quality` subagent for best practices
3. Make code fixes based on identified issues
4. Re-run the workflow: `npx output workflow run <workflowName> <input>`
5. Verify the fix with a new trace

Files: 1

Size: 4.5 KB

Complexity: 13/100

Category: Backend & APIs

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

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