The UI
The web UI is built and embedded in the orchestrator binary. It uses the industry-standard words
for durable execution: Workflows, Activities, Workers, Task Queues and Signals. Cross-team calls
are Services (Service Endpoints and Service Calls). The Kotlin port and the lertha CLI name
some of these more briefly; the Glossary maps them.
What to look at
- A Workflow's history is the recorded sequence of events: Activity scheduled, started, completed, timer started, Signal received. Every row names the Worker identity that produced it, which is how you see a Workflow started on one Worker and finished on another.
- Attempts on a failed Activity show each error and the interval before the next try.
- Standalone Activities is the job-queue view: every Activity started directly from application code.
- Workers → Deployments is where Serverless Workers are set up.
Access
The UI has its own sign-in: a six-digit code emailed to an allowed address, then a session cookie. Every page and API call behind it needs that session.