Reference

Runs

Source ExecutionsPage.tsx, WorkQueuePage.tsx, WorkQueueDetailPage.tsx, DeadLettersPage.tsx, DeadLetterDetailPage.tsx

One list of runs, with four views as tabs across the top. Each view is its own address, and its filters are in the address too.

ViewRouteLists
All/runsEvery run, newest first
Failed/runs?state=FAILEDAll runs filtered to Failed, with where and why each failed
Queued/runs/queuedThe work queue: runs asked for and waiting for a worker, and entries already dispatched or cancelled
Dead letters/runs/dead-lettersManifests whose runs failed until their retries ran out

A run's own page is A run.

All and Failed

Read through operations.executions, 25 rows a page, paged by cursor. The total under the list can be an estimate on an unfiltered list.

ColumnValue
TrainThe train's short name, linking the run
RunThe run's id
StatePending, In progress, Completed, Failed or Cancelled, and cancelling once a cancel was requested
Started, DurationWhen it started, and how long it took once it ended
Running junctionThe step an in-progress run is on, on a host that records junction progress
ManifestThe manifest that scheduled it
ParentThe run that started it
Failure classTransient, Conflict, Permanent or Unclassified, for a failed run (failure classification)

The Failed view replaces Running junction with Failed at (the junction) and Reason.

FilterAddressMatches
Train nametrainPart of the train's name
StatestateOne state
OrderorderNewest or oldest first
Failure classfailureOne class
After, Beforeafter, beforeStarted in the range, in the browser's time zone
External idexternalIdExactly that external id
Parent idparentIdThe runs that run started
Host namehostExactly that host's runs
Hide scheduler trainsLeaves out the scheduler's own trains; a filter that names a train shows it whatever this says

Beside the list, Live feed shows the last 100 run state changes as they happen. On the first page of an unfiltered list, new runs and state changes are merged into the rows as they arrive.

Cancel selected requests cancellation of the ticked Pending and In progress runs, after a confirmation, through cancelExecutions: a queued run never starts, and a running one stops at its next junction. The answer counts what was flagged and says why any was skipped. With the list filtered to Pending or In progress, Cancel all N matching cancels every run the filter matches as a bulk operation.

Queued

The work queue, read through operations.workQueue.

ColumnValue
Train, EntryThe train, and the entry's id, each linking the entry
StatusQueued, Dispatched or Cancelled
Created, Priority, AttemptsWhen it was queued, its dispatch priority, and how many times dispatch tried it
SubjectThe entry's subject key, when the train sets one. Entries with one subject run one at a time. Clicking it filters the list to that subject. Computed by your train, so it may carry record identifiers.
ConfirmedYes, or Staged for a queued entry whose train's queue check has not finished, which dispatch does not take yet
Manifest, Run, ReplaysThe manifest that queued it, the run it started once dispatched, and the run whose recorded decisions its run replays

Filters: train name, Subject (exact), Manifest id, Status. Queue train opens the Queue dialog. Cancel on a queued row, or Cancel selected, cancels entries after a confirmation; their runs never start. An entry a user's state-machine draft queued is read-only to operators, and the refusal says so.

A queued entry

/runs/queued/{id}, read through workQueue.detail: its id, external id, train, status, priority, dispatch attempts, when it was created, scheduled, dispatched and confirmed, its subject, input type, manifest, run, the run it replays decisions of ("None: it asks afresh" when none), and the dead letter it requeues. Waiting on says which entry holds its subject: "Entry N, which is running for the same subject", or "Entry N, which is ahead of it for the same subject". The input is shown with its [TraxSensitive] members masked by the API. Cancel entry is offered while it is queued.

Dead letters

Read through operations.deadLetters. How to resolve one is in Resolve a dead letter.

The view shows dead letters By train and reason by default, or as a List (view=list). The grouped view reads the newest 500 and groups those whose train and reason are the same; a group names its train, how many it holds and how many still await, its manifests, and when the latest came. A group of one shows its row; a larger group opens on a click. When more than 500 match, the page says so and links the list, which pages through every one.

ColumnValue
Train, Dead letterThe manifest's train, and the dead letter's id, each linking the dead letter
ManifestThe manifest, by its external id
StatusAwaiting intervention, Retried or Acknowledged
Reason, Retries, Dead-letteredWhy, the retry count it reached, and when

Filters: Manifest id, Status.

ActionDoes
Requeue (a row)Queues a new run of its manifest and marks the dead letter Retried
Acknowledge (a row)Asks for a resolution note and marks it Acknowledged, without a retry
Requeue selected, Acknowledge selectedThe same for the ticked rows that await intervention
Requeue allRequeues every dead letter awaiting intervention, in the background on the server, after the word all is typed; the page follows the job and reports its count
Acknowledge allAsks for a note and acknowledges every one awaiting intervention
Requeue all N matching, Acknowledge all N matchingWith the list filtered to Awaiting intervention, a bulk operation over what the filter matches

Each requeue has a , ask afresh twin, offered when a listed train asks a decider: the new run asks its deciders again instead of replaying the failed run's decisions.

A dead letter

/runs/dead-letters/{id}.

SectionShows
Dead letter detailsStatus, when it was dead-lettered, the retry count it reached, when and how it was resolved, its manifest (with a link to that manifest's dead letters), the run its retry started, and the reason
ManifestThe manifest's name, whether it is enabled, its schedule, max retries, timeout, priority and last successful run
Most recent failureThe latest failed run: its id, failure junction, exception, failure class, reason, times, stack trace and input
Failed run historyThe manifest's failed runs, a page at a time, each linking its run

While it awaits intervention it offers Requeue, Requeue, ask afresh and Acknowledge.