Post-Execution Workflow
Inspect a Finished Pipeline Run.
This is an older version of the ZenML documentation. To check the latest version please visit https://docs.zenml.io
Post Execution Workflow
After executing a pipeline, the user needs to be able to fetch it from history and perform certain tasks. This page captures these workflows at an orbital level.
Accessing past pipeline runs
In the context of a post-execution workflow, there is an implied hierarchy of some basic ZenML components:
Repository
The highest level Repository
object is where to start from.
Pipelines
The repository contains a collection of all created pipelines with at least one run sorted by the time of their first run from oldest to newest.
The pipeline name is the name of the decorated function (or the Pipeline class in case of the Class Based API).
Be careful when accessing pipelines by index. Even if you just ran a pipeline it might not be at index -1
, due to the fact that the pipelines are sorted by time of first
run. As such it is recommended to access the pipeline by its name
Runs
Each pipeline can be executed many times. You can easily get a list of all runs like this
Steps
Within a given pipeline run you can now zoom in further on the individual steps.
The steps are ordered by time of execution. Depending on the orchestrator, steps can be run in parallel. As such, accessing steps by index can be unreliable across different runs. Instead, it makes sense to access steps by their name.
The step name is the name of the decorated function (or the Step
class in case of the class-based API).
Outputs
Most of your steps will probably create outputs. You'll be able to inspect these outputs like this:
The names of the outputs can be found in the Output
typing for your steps:
Last updated