-
In Airflow 2.3.4 and other old versions, there was a very simple trigger form which received a major upgrade lately. So in Airflow 2.3.4 if you manually triggered the DAG from the UI with the Right-Arrow ICON (up rigth corner), you in fact had a choice:
With this, if you wanted, you could select "Trigger DAG w/config" and then set the Logical date using the date picker. The main point here: You could ALWAYS select "Trigger DAG w/config" even if the DAG had no Dag params defined at all and thus CHANGE the Logical Date! Now in Airflow 2.8.3, if you want to trigger a Dag manually via the UI using the Right-Arrow ICON, if there is no Dag params defined in the Dag, the Trigger Form does not open at all, so via UI you simply cannot run a Dag with a different logical Date. Could it be that by introducing the New Trigger Form accidently the capability was lost to set the logical date for DAGs that have no dag params defined? If yes, is this a bug? Is there a way, to always open the Trigger Form? In that case, actually one can set the logical date using the date picker in the section "Generated Configuration JSON and Dagrun Option". |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
DagRun trigger for for non parametrised DAGs is disabled by default since Airflow 2.7, for enable it you need set Additional links for the reference: |
Beta Was this translation helpful? Give feedback.
DagRun trigger for for non parametrised DAGs is disabled by default since Airflow 2.7, for enable it you need set
[webserver] show_trigger_form_if_no_params
configuration toTrue
Additional links for the reference: