DagsterTriggeredRun class represents a Metaflow run that was triggered through a Dagster deployment. It provides access to run status, the Metaflow Run object, and links to the Dagster UI.
Properties
The Metaflow pathspec for this run in the format
FlowName/dagster-<run_id>.The run ID portion corresponds to the Dagster run UUID, which can be used to locate the run in the Dagster UI.A simple status string based on the underlying Metaflow run.Returns:
"PENDING"- The run has not yet appeared in Metaflow’s metadata"RUNNING"- The run is currently executing"SUCCEEDED"- The run completed successfully"FAILED"- The run finished but was not successful
The Metaflow Run object for this triggered run.This property polls Metaflow until the run with the given pathspec appears. It applies deployer environment variables so local metadata works correctly. Returns
None if the run has not yet appeared in the metadata.Once the Run object is available, you can access all standard Metaflow Run properties and methods such as:run.data- Access artifacts from the runrun.successful- Check if the run completed successfullyrun.finished- Check if the run has finishedrun.steps- Iterate through run steps
URL to the Dagster UI for this run, if available.Returns a link to the local Dagster UI (
http://localhost:3000) by default. The run ID embedded in the Metaflow pathspec is extracted and used to construct the URL.Returns None if the pathspec format is unexpected.Usage Examples
Basic Usage
Trigger a run and monitor its status:Accessing Run Data
Wait for the run to complete and access its data:Monitoring Multiple Runs
Trigger multiple runs and monitor them:Opening Dagster UI
Get the Dagster UI link for a triggered run:Inheritance
DagsterTriggeredRun inherits from metaflow.runner.deployer.TriggeredRun, which provides the base run property that polls Metaflow until the run with the given pathspec appears. The Dagster implementation adds the status and dagster_ui properties for convenience.