Operations

Debugging Workflows


Orcher provides CLI tools and database-backed logs for debugging workflow executions. You can inspect execution state, view the event-sourced journal, stream real-time logs, query task execution details, and understand replay behavior — all without modifying your workflow code.

  • Describe resources — orcher describe shows detailed workflow, task, and execution information
  • View logs — orcher logs streams text logs, journal entries, or task execution details
  • Workflow history — orcher workflow history shows the event-sourced journal for replay analysis
  • Execution management — Cancel, terminate, or send events to running workflows

Inspecting Executions

Describe a Workflow Execution

Use orcher describe (alias: desc) to get detailed information about a workflow execution:

1
orcher describe workflow my-workflow-id

This shows execution status, input/output, timing, and step-level details fetched from the orchestrator.

List Workflow Executions

Filter and list executions:

1
# List all executions
2
orcher workflow list
3
4
# Filter by status
5
orcher workflow list --status running
6
orcher workflow list --status failed
7
8
# Filter by workflow name
9
orcher workflow list --workflow order-processing

Get Execution Details

Get detailed info about a specific execution:

1
# Detailed execution info (aliases: describe, info)
2
orcher workflow get <execution-id>

Next Steps

  • Viewing Logs — Text logs, journal entries, task execution details, and workflow history
  • Understanding Replay — How deterministic replay works and how to debug it
  • Scenarios & Management — Managing running workflows, common debugging scenarios, and CLI reference
  • Logging — Configure structured logging formats
  • Metrics — Monitor performance with Prometheus
  • Tracing — Distributed tracing with OpenTelemetry