Keith Devens01/26/2022, 4:51 PM
. The existing code expects that resumes maintain the same run id (which determines working directories and so on). Is there an id in Dagster that uniquely identifies a run across resumes? I see references to a `root_run_id`…
prha01/26/2022, 5:02 PM
(as you have identified). If you keep retrying runs, each new run will have the last attempted run as a
, while keeping the original run id as the root. This run group shows up in the right side panel on the Run view, showing the run lineage. I’m not sure if that will serve your purpose. There is not a run id that uniquely identifies the entire group, but I can get the set of runs from the run group based on the common root run id.
Keith Devens01/26/2022, 5:07 PM
from the Context and setting it in the environment for the called process. I don’t see
documented for Contexts (https://docs.dagster.io/_apidocs/execution#contexts) but I’ll experiment and see if it’s on there.
does, but it’s null when starting out. So, the parent run is the immediately preceding run to this one in a chain, and all can be part of a group that’s represented by the root run id, but that’s only set if there’s been a resume?
prha01/26/2022, 5:18 PM
Keith Devens01/26/2022, 5:20 PM
== the original
, then that should get me what I need. Experimenting.
should always be set, and should == the
if it’s the first run?
prha01/26/2022, 5:30 PM
Keith Devens01/26/2022, 5:42 PM