tanelk opened a new issue, #33164:
URL: https://github.com/apache/airflow/issues/33164
### Apache Airflow version
2.6.3
### What happened
When rerunning a DAG run with dynamically mapped tasks and the number of
mapped task instances degreases, then downstream tasks with all_success trigger
rule (likely some others as well) will not get scheduled, because removed
status is not considered to be successful. When a regular task gets removed,
then this does not happen, because it will get removed from the DAG structure.
Task dependency message
```Task's trigger rule 'all_success' requires all upstream tasks to have
succeeded, but found 2 non-success(es).
upstream_states=_UpstreamTIStates(success=22, skipped=0, failed=0,
upstream_failed=0, removed=2, done=24), upstream_task_ids={'upstream_task'}```
Previously you could forcefully run it with the "run" button in UI, but it
has been removed in one of the resent releases.
Luckily I could delete the removed TIs and then the downstream tasks got
rescheduled, but this is not "scalable".
### What you think should happen instead
_No response_
### How to reproduce
-
### Operating System
-
### Versions of Apache Airflow Providers
_No response_
### Deployment
Virtualenv installation
### 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
- [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]
