Workflows Glossary

Workflows automate machine learning tasks, combining GPU instances with an expressive syntax to generate production-ready machine learning pipelines with a few lines of code.


This glossary defines the core concepts behind Paperspace Workflows to help build your mental model of how workflows work and understand what the documentation is referring to when it uses certain terminology.

An Action is a self-contained, composable set of code building blocks that can perform specific actions within a machine learning project. Actions can receive parameters (e.
Job
A Job is a self-contained part of a workflow spec that is similar to an Argo step. Jobs can define inputs, outputs, and their own environment variables.
A Workflow is a named or unnamed entity that belongs to a team and project. Named workflows can be re-run with a default workflow spec, or be passed a new spec every time.
Workflow Run: the implementation of a workflow The most basic run requires a workflowId and clusterId - most will also include a workflow spec, and the inputs to be passed into the workflow The workflow run contains everything needed for the workflow to actually be executed, i.
A Workflow Spec is a YAML list of jobs that is converted into an Argo template and run on the Gradient distributed runtime engine.