Skip to content

DAGs with required object type param cannot be triggered with default None #55213

Closed

Description

@softwaredevPK

Apache Airflow version

2.11.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

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.

Image

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") `

Operating System

Ubuntu 22.04.4 LTS

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. boring-cyborg commented on Sep 3, 2025

    @boring-cyborg

    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.

  2. added
    area:UIRelated to UI/UX. For Frontend Developers.
    on Sep 3, 2025
  3. shreyaskj-0710 commented on Sep 4, 2025

    @shreyaskj-0710
    Contributor

    I would like to work on this issue--Let me know if it's being picked by someone else.

  4. potiuk commented on Sep 4, 2025

    @potiuk
    Member

    Feel free.

  5. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @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.

  6. bbovenzi commented on Oct 1, 2026

    @bbovenzi
    Contributor

    This is Airflow 2 and otherwise closed by #71710

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions