Hello! I’m using run retries for some of my jobs. In my DAG, I’m determining if the current run is a retried run by looking for the

parent-run-id

in the op context object. However, that field is set for both automatic run retries and user-initiated retries in the Dagster UI. Is there a programmatic way to differentiate between automatic retries vs user retries?

Hi Will. Unfortunately I don't think we have a built-in way to detect automatic vs user-initiated retries. The

parent_run_id

field is automatically set for all run retries to point to the root run. Not a great solution, but you could add a tag when you do manually retry a run via Dagit. I can also imagine that Dagit can add the tag when a user initiates a retry manually, though we don't have this functionality currently. If this is an important feature for you, I'd suggest filing a feature request for this!