Run
Status
SUCCEEDED
Workflow
data-pipeline v1
Run id
e1a8ee6c-5bb4-442a-8570-5aceb2ce1065
Seed
3024093237604488000
Duration
47ms
What the journal proves
4
Attempts
1
Workers involved
0
Faults injected
0
Leases expired
0
Tasks requeued
0
Retries scheduled
0
Workers lost
0
Effects suppressed
0
Dead-lettered
·
Recovery
Every number above is a count of events in this run’s journal. Recovery is measured from the first fault, lease expiry, task failure or lost worker to the run completing, the same interval relab test asserts on.
Tasks
| Status | Task | Attempt | Worker | Error |
|---|---|---|---|---|
| SUCCEEDED | analyze | 1/3 | 45cf93e9 | · |
| SUCCEEDED | import | 1/3 | 45cf93e9 | · |
| SUCCEEDED | report | 1/3 | 45cf93e9 | · |
| SUCCEEDED | validate | 1/3 | 45cf93e9 | · |
Timeline
The run’s complete recorded history, in sequence order. This is the same journal relab replay reduces. Filtering hides rows from this view; it never changes the sequence numbers, so a gap in them is still a gap.
No worker events in this run. That is a fact about the run, not a missing page: nothing of that kind was recorded.