Viewing Logs
The orcher logs command retrieves three types of execution data from the server.
Text Logs (Default)
Human-readable logs from the workflow_execution_logs table:
1# View recent logs for a workflow2orcher logs workflow/my-workflow34# Follow logs in real-time (SSE streaming)5orcher logs workflow/my-workflow --follow67# Filter by log level8orcher logs workflow/my-workflow --level error910# Filter by time range11orcher logs workflow/my-workflow --since "2024-01-15T10:00:00Z"1213# Search logs14orcher logs workflow/my-workflow --grep "payment failed"1516# Show last N entries17orcher logs workflow/my-workflow --tail 50Journal Entries
View the event-sourced journal — every step recorded for replay protection:
1orcher logs workflow/my-workflow --journalThis shows the sequence of journaled events: WorkflowStarted, StepCompleted, TimerFired, EventReceived, WorkflowCompleted, etc. Useful for understanding exactly what happened during execution and what would be replayed on recovery.
Task Execution Details
View task-level execution records from the task_executions table:
1orcher logs workflow/my-workflow --tasksThis shows each task's status, duration, retry count, and result.
Workflow History
The orcher workflow history command (aliases: journal, events) provides another way to view the execution journal:
1orcher workflow history <execution-id>Next Steps
- Debugging Overview — Inspecting executions with describe, list, and get commands
- 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