omarsmak commented on issue #23911: URL: https://github.com/apache/airflow/issues/23911#issuecomment-1139357357
> Skipped sounds wrong because a skipped task means it _won’t_ run. Success is technically correct since there’s no failure. What is the part you find this is confusing? If it’s the UI, we can probably do something just in the UI to signify a run is “empty” without touching the database definition. If it’s the API, maybe we can add an additional field to make it more obvious to the user that no tasks were actually run. The confusing part is the API, when I query the DAGRuns through the REST APIs for a particular DAG, I get for those DAGRuns that didn't run a `success` which is _really_ misleading since no tasks have ran for the particular DAG. Regarding the Skipped status, this is just an idea, if there is an extra field or different status that tells me nothing has ran, I think this would suffice. What kind of additional field you have in mind to add? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
