[auto run retry tags] 3/n - when a run is retried, add the did_retry tag

dagster-io / dagster

An orchestration platform for the development, production, and observation of data assets.

Apache License 2.0

11.79k stars 1.48k forks source link

Summary & Motivation

Adds a dagster/did_retry tag to any run that had a retry launched by the auto run reexecution daemon. This allows us to determine if a run is waiting to be retried by looking at the values of dagster/will_retry and dagster/did_retry

Examples: dagster/will_retry=False - no retry will be launched for this run dagster/will_retry=True - a retry will be launched for this run, but has not been launched yet dagster/will_retry=True and dagster/did_retry=True - a retry has been launched for this run

associated internal pr https://github.com/dagster-io/internal/pull/12787

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

dagster-io / dagster