Skip to main content

Glossary

View Markdown

The port, the lertha CLI, the UI and this site use the Lertha words. The core underneath has its own identifiers, which show up in query filters, event histories and raw CLI output. This table maps them so nothing on a screen is a mystery.

LerthaCore identifierNote
TaskActivity, ActivityType, ActivityIdone unit of work; started from code or from a flow
Standalone Taskstandalone Activitya task started directly from application code
FlowWorkflow, WorkflowType, WorkflowIdthe durable program
Run, RunIdWorkflowId / ActivityIdthe id you chose; one execution of a task or a flow
Flow RunWorkflowExecution
Task RunActivityExecution
Run ID (in the UI)RunIdthe core's per-attempt execution id, distinct from your RunId
QueueTaskQueue
RunnerWorkerthe process that polls a queue
SignalSignal, WorkflowExecutionSignaled
attemptTimeoutStartToCloseTimeout
overallTimeoutScheduleToCloseTimeout
heartbeatTimeoutHeartbeatTimeout
ConflictPolicyid conflict policyFAIL, USE_EXISTING
ReusePolicyid reuse policyALLOW_DUPLICATE, ALLOW_DUPLICATE_FAILED_ONLY, REJECT_DUPLICATE
NonRetryableTaskErrornon-retryable failure
Services, Service Endpoint, Service CallNexus, NexusEndpoint, NexusOperationcross-team calls
Orchestratorthe service
lertha task runactivity executelertha raw -- ... passes arguments to the core untouched
lertha flow historyworkflow show
LERTHA_ADDRESS, LERTHA_NAMESPACE--address, --namespace

Query syntax

List filters use the core's field names: ActivityType = "ComposeGreeting", WorkflowType = "AgentRun", ExecutionStatus = "Running", WorkflowId = "agent-42".