client.workflow_run
The workflow run is an instance of a workflow.
Attributes
Classes
A utility class responsible for instantiating workflow run objects. |
|
WorkflowRun enables tracking for multiple runs of a single Workflow. |
Module Contents
- class client.workflow_run.WorkflowRunFactory(workflow_id: int, requester: jobmon.core.requester.Requester | None = None)[source]
A utility class responsible for instantiating workflow run objects.
This class sends the appropriate resume signals so that the parent workflow object is in a state where the newly created workflowrun is ready to run, either on resume or not.
- set_workflow_resume(reset_running_jobs: bool = True, resume_timeout: int = 300) None[source]
Set statuses of the given workflow ID’s workflow to a resumable state.
Move active workflow runs to hot/cold resume states, depending on reset_running_jobs.
- class client.workflow_run.WorkflowRun(workflow_id: int, requester: jobmon.core.requester.Requester | None = None, workflow_run_heartbeat_interval: int | None = None, heartbeat_report_by_buffer: float | None = None)[source]
Bases:
objectWorkflowRun enables tracking for multiple runs of a single Workflow.
A Workflow may be started/paused/ and resumed multiple times. Each start or resume represents a new WorkflowRun.
In order for a Workflow can be deemed to be DONE (successfully), it must have 1 or more WorkflowRuns. In the current implementation, a Workflow Job may belong to one or more WorkflowRuns, but once the Job reaches a DONE state, it will no longer be added to a subsequent WorkflowRun. However, this is not enforced via any database constraints.