Operations

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 workflow
2
orcher logs workflow/my-workflow
3
4
# Follow logs in real-time (SSE streaming)
5
orcher logs workflow/my-workflow --follow
6
7
# Filter by log level
8
orcher logs workflow/my-workflow --level error
9
10
# Filter by time range
11
orcher logs workflow/my-workflow --since "2024-01-15T10:00:00Z"
12
13
# Search logs
14
orcher logs workflow/my-workflow --grep "payment failed"
15
16
# Show last N entries
17
orcher logs workflow/my-workflow --tail 50

Journal Entries

View the event-sourced journal — every step recorded for replay protection:

1
orcher logs workflow/my-workflow --journal

This 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:

1
orcher logs workflow/my-workflow --tasks

This 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:

1
orcher workflow history <execution-id>

Next Steps