You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
DAGs with required object type param cannot be triggered with default None #55213
If a DAG contains "object" Param having not having default set, then the manual triggering for it doesn't succeed. In this case, If I push "Trigger" button in UI, it just doesn't react (of course this field is filled manually).
I noticed that the reason is because the text that I write is not copied into hidden , and therefore validation error arise, but as this field is hidden, there is no information for user, and its clearly a bug.
What you think should happen instead?
There is clearly an error in console probably connected to this issue.
How to reproduce
`from airflow import DAG
from airflow.operators.dummy import DummyOperator
from airflow.models import Param
with DAG(
"run-test",
params={
"object_param": Param( type="object", description="Object field"),
},
schedule=None,
catchup=False,
) as dag:
DummyOperator(task_id="dummy_task") `
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
Activity
boring-cyborg commentedon Sep 3, 2025
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
shreyaskj-0710 commentedon Sep 4, 2025
I would like to work on this issue--Let me know if it's being picked by someone else.
potiuk commentedon Sep 4, 2025
Feel free.
potiuk commentedon Mar 2, 2026
@shreyaskj-0710 We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
bbovenzi commentedon Oct 1, 2026
This is Airflow 2 and otherwise closed by #71710