TJaniF opened a new issue, #63734:
URL: https://github.com/apache/airflow/issues/63734
### Apache Airflow version
main (development)
### If "Other Airflow 3 version" selected, which one?
_No response_
### What happened?
Filing for @Lee-W
The draft docs for partitioned assets state:
> Partitioned events are intended for partition-aware downstream scheduling,
and do not trigger non-partition-aware Dags.
But this does not seem to be true currently.
Dags:
```python
from airflow.sdk import dag, Asset, task, CronPartitionTimetable
asset_1 = Asset("asset_1")
@dag(schedule=CronPartitionTimetable("* * * * *", timezone="UTC"))
def asset_1_dag():
@task(outlets=[asset_1])
def task_1():
return "hi"
task_1()
asset_1_dag()
@dag(schedule=asset_1)
def regular_asset_dag():
@task
def task_1():
return "hi"
task_1()
regular_asset_dag()
```
The regular_asset_dag gets triggered by the partitioned asset update:
<img width="399" height="495" alt="Image"
src="https://github.com/user-attachments/assets/ff016a48-8e00-4d9d-8b5f-58f10259599c";
/>
This also happens for manual updates to the asset.
<img width="465" height="457" alt="Image"
src="https://github.com/user-attachments/assets/5add92a5-f198-4ff7-99ff-2edf35207398";
/>
### What you think should happen instead?
If the docs are correct then the downstream Dag should not be scheduled. Or
if this intended behavior then the docs need to be updated.
### How to reproduce
1. Add the Dags above
2. Unpause the regular_asset_dag
3. Unpause the asset_1_dag
4. See the regular_asset_dag run
### Operating System
Mac Tahoe 26.2
### Versions of Apache Airflow Providers
-
### Deployment
Other
### Deployment details
breeze
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
