github.com/pachyderm/pachyderm@v1.13.4/doc/docs/1.9.x/concepts/pipeline-concepts/datum/datum-processing-states.md (about)

     1  # Datum Processing States
     2  
     3  When a pipeline runs, it processes your datums.
     4  Some of them get processed successfully and some might
     5  be skipped or even fail. Generally, processed datums
     6  fall into either successful or failure state category.
     7  
     8  The following table describes the processing states
     9  of datums that can occur in Pachyderm:
    10  
    11  **Successful States**
    12  
    13  | State      | Description |
    14  | ---------- | ----------- |
    15  | Successful | The datum has been successfully processed in this job. |
    16  | Skipped    | The datum has been successfully processed in a previous job, has not changed since then, and therefore, it was skipped in the current job. |
    17  
    18  **Failure States**
    19  
    20  | State      | Description |
    21  | ---------- | ----------- |
    22  | Failed     | The datum failed to be processed. Any failed datum in a job fails the whole job. |
    23  | Recovered  | The datum failed, but was recovered by the user's error handling code. Although the datum is marked as *recovered*, Pachyderm does not process it in the downstream pipelines. A recovered datum does not fail the whole job. Just like failed datums, recovered datums are retried on the next run of the pipeline. |
    24  
    25  You can view the information about datum processing states in the output of
    26  the `pachctl list job` command:
    27  
    28  ![datums in progress](../../../assets/images/datums_in_progress.svg)
    29  
    30  !!! note
    31      Datums that failed are still included in the total, but not
    32      shown in the progress indicator.