Skip to main content
LlamaIndex Workflows are a building block for complex, event-driven LLM applications — each @step is a typed handler that emits the next event. Arize AX captures every workflow run — each step invocation, the events flowing between them, and the LLM calls made inside steps — via the openinference-instrumentation-llama-index package, the same instrumentor that covers core LlamaIndex.
If you’ve already followed the LlamaIndex tracing guide, workflows are already traced — there is one instrumentor for both. This page is a workflow-focused setup that you can follow standalone.

Prerequisites

Launch Arize AX

  1. Sign in to your Arize AX account.
  2. From Space Settings, copy your Space ID and API Key. You will set them as ARIZE_SPACE_ID and ARIZE_API_KEY below.

Install

Configure credentials

Setup tracing

Run LlamaIndex Workflows

Expected output

Verify in Arize AX

  1. Open your Arize AX space and select project llamaindex-workflows-tracing-example.
  2. You should see a new trace within ~30 seconds containing a OceanFactWorkflow.run parent span wrapping a step span (OceanFactWorkflow.answer) and a nested OpenAI.acomplete LLM child span with the prompt, response, and token usage attached.
  3. If no traces appear, see Troubleshooting.

Check from the skill, CLI, or SDK

Confirm spans are actually reaching your Arize AX project. Use whichever fits your workflow — the skill and CLI work for any framework; the SDK check is shown for each language.
Install the Arize Skills plugin and let your coding agent check for you:
Then prompt your agent:
Use the arize-trace skill to export and analyze recent traces from my project. Confirm spans are arriving, and summarize any errors or latency issues.

Troubleshooting

  • No traces in Arize AX. Confirm ARIZE_SPACE_ID and ARIZE_API_KEY are set in the same shell that runs example.py. Enable OpenTelemetry debug logs with export OTEL_LOG_LEVEL=debug and re-run.
  • Workflow ran but no spans appear. LlamaIndexInstrumentor().instrument(...) must run before any llama_index import. Make sure instrumentation.py is the first import in your entry point.
  • 401 from OpenAI. Verify OPENAI_API_KEY is set and has access to gpt-5.5. Swap for a model your key can call.
  • Step did not return a StopEvent. Workflows finish only when a step returns StopEvent (or StartEvent rolls into a chain that eventually does). Check each @step’s return type.
  • WorkflowTimeoutError: Operation timed out after N.0 seconds. LlamaIndex Workflow has its own timeout — 45 s by default — separate from any HTTP-client timeout your LLM library uses. Reasoning-heavy models (gpt-5.5, o3, etc.) can blow past that on the first call. Pass timeout=180 (or similar) to the workflow constructor as shown in the Run section.

Resources

LlamaIndex Workflows Documentation

OpenInference LlamaIndex Instrumentor

LlamaIndex Tracing Guide