Skip to main content

The UI

View Markdown

The web UI is built and embedded in the orchestrator binary. It speaks the port's vocabulary: Flows, Tasks, Runs, Services. Routes, query fields and event type names are the core's identifiers, so a run's history reads WorkflowExecutionSignaled where the page says Flow; the Glossary maps them.

What to look at​

  • A run's history is the recorded sequence of events: task scheduled, started, completed, timer started, signal received. Every row names the worker identity that produced it, which is how you see a run started on one worker and finished on another.
  • Attempts on a failed task show each error and the interval before the next try.
  • Standalone Tasks is the job-queue view: every task started directly from application code.

Access​

Behind the platform's auth in production. The UI has no user accounts of its own.