Workflow v3.stages
Stage types in a read-only workflow graph snapshot.
Identity and outgoing connections for one stage in the loaded graph.
Iterate permitted current tasks, fetching pages lazily without assigning work.
Invalid status and sort values are rejected immediately. Backend validation
and request errors occur during iteration. This is a changing queue, not
a snapshot. Terminal stages use newest-arrival ordering and reject both
statuses and sort arguments.
Background processing at workflow entry.
Manual annotation of targets.
Submit Annotation tasks at this stage atomically; save labels separately first.
Pathway selection, comments and permissions follow AnnotationTask.submit().
One pathway and optional comment apply to every task. Empty batches raise
ValueError; the backend enforces batch limits. Leaves snapshots unchanged;
sent requests are not automatically retried.
Manual review of targets and labels.
Submit tasks atomically without changing individual label decisions.
Tasks must be at this stage. Pathway selection, comments and permissions
follow ReviewTask.submit(). One pathway and optional comment apply to every
task. Empty batches raise ValueError; the backend enforces batch limits.
Leaves snapshots unchanged; sent requests are not automatically retried.
Work held for an external integration.
Submit External tasks at this stage atomically through one pathway.
Pathway selection and permissions follow ExternalTask.submit(). Empty
batches raise ValueError; the backend enforces batch limits.
Leaves snapshots unchanged; sent requests are not automatically retried.
Terminal stage for the Complete outcome.
Terminal stage for the Archive outcome.
Terminal stage for the Skip outcome.
Targets are routed by the configured pathway allocations.
Route targets using the user who last processed them at a manual stage.
An unfamiliar stage available for discovery, not specialized operations.
Was this page helpful?

